Bug 688885

Summary:	yast2 kdump module: boot partition existence is not checked in advance
Product:	[openSUSE] openSUSE 11.4	Reporter:	macias - <bluedzins>
Component:	YaST2	Assignee:	Forgotten User kWxJsf0s20 <forgotten_kWxJsf0s20>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	jreidinger
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.4
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description macias - 2011-04-20 18:22:46 UTC

Yast2 Kdump modules assumes (but does not check it) that boot partition is present and it just ok to write changes for Grub.

Well, if you do any I/O operations, you should always check if partition/file/disk is present before accessing it. Otherwise user sees unwanted errors and ends up with unclear state -- is the entries (for grub) will be deleted? Remembered and restored? Is it ok to run kdump again?

Comment 1 Zhi Juan Jia 2011-04-21 02:28:01 UTC

Please attach y2logs. If you are in doubt follow:
http://en.opensuse.org/openSUSE:Bugreport_YaST
Thanks!

Comment 2 macias - 2011-04-21 17:48:17 UTC

Here it is:
https://bugzilla.novell.com/attachment.cgi?id=425480

Comment 3 Josef Reidinger 2016-10-06 13:32:57 UTC

There is not enough resources for such change ( 6 years without change ), so reassigning to yast-community hoping that someone from community will fix this issue.

Comment 4 Tomáš Chvátal 2017-08-12 09:35:15 UTC

This is rather enhancement request than a bug.

Please report a bug against yast2-kdump on https://github.com/yast/yast2-kdump 
Preferred is even pullrequest given the amount of resources devoted to this module.

Comment 5 macias - 2017-08-14 13:38:08 UTC

a) it would mean that corrupting the system is new "normal", and feature is fixing such bug

b) as Michael Andres wrote in similar report (https://bugzilla.opensuse.org/show_bug.cgi?id=485945) " It makes no sense to convert a zypp bugzilla entry into a zypp github issue. Especially as our package submission policy asks for bugzilla references in the changes file, we preferably track in bugzilla."

It is really not helpful if we start just shifting reports from one site to another, it takes extra time and serves no purpose other than "oh, our stats look good, bugs count decreased".

Comment 6 Tomáš Chvátal 2017-08-15 17:25:14 UTC

Well then move the product and manage your bug properly. This is not per-se issue of 11.4 openSUSE release. As stated by Josef there won't be resources devoted to this by suse so you can either implement it or properly manage the request and move it to right codestream.