Bug 118218 - Presence of package yast2-storage-evms causes YaST modules to hang
Summary: Presence of package yast2-storage-evms causes YaST modules to hang
Status: VERIFIED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 4
Hardware: i386 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Thomas Fehr
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-21 14:35 UTC by Stefan Hundhammer
Modified: 2008-09-02 18:08 UTC (History)
1 user (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2logs.tgz (12.69 KB, application/x-tgz)
2005-09-21 14:38 UTC, Stefan Hundhammer
Details
hwinfo (199.68 KB, text/plain)
2005-09-21 14:39 UTC, Stefan Hundhammer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Hundhammer 2005-09-21 14:35:57 UTC
If package yast2-storage-evms is installed, some YaST modules hang upon startup.   
The last lines in y2log are:   
   
2005-09-21 16:24:46,144 INFO  libstorage - Container.cc(Container):25 constructed   
cont md   
2005-09-21 16:24:46,144 INFO  libstorage - MdCo.cc(MdCo):21 constructing MdCo   
detect:1   
2005-09-21 16:24:46,144 INFO  libstorage - AsciiFile.cc(loadFile):48 Loading   
File:"/etc/raidtab"   
2005-09-21 16:24:46,144 INFO  libstorage - AsciiFile.cc(loadFile):48 Loading   
File:"/etc/mdadm.conf"   
2005-09-21 16:24:46,144 INFO  libstorage - MdCo.cc(getMdData):85 begin   
2005-09-21 16:24:46,144 INFO  libstorage - MdCo.cc(~MdCo):36 destructed MdCo   
2005-09-21 16:24:46,145 INFO  libstorage - Container.cc(~Container):34 destructed   
cont /dev/md   
2005-09-21 16:24:46,145 INFO  libstorage - SystemCmd.cc(SystemCmd):27   
Konstruktor SystemCmd:"vgdisplay -s" Nr:0   
2005-09-21 16:24:46,145 INFO  libstorage - SystemCmd.cc(execute):96 SystemCmd   
Executing:"vgdisplay -s"   
2005-09-21 16:24:46,152 INFO  libstorage - SystemCmd.cc(addLine):561 Adding Line   
1 "/bin/sh: vgdisplay: command not found"   
2005-09-21 16:24:46,152 INFO  libstorage - SystemCmd.cc(getUntilEOF):527   
pid:30267 added lines:1 stderr:1   
2005-09-21 16:24:46,153 INFO  libstorage - SystemCmd.cc(doExecute):241 system()   
Returns:127   
2005-09-21 16:24:46,153 INFO  libstorage - SystemCmd.cc(logOutput):572   
stderr:/bin/sh: vgdisplay: command not found   
2005-09-21 16:24:46,153 INFO  libstorage - LvmVg.cc(getVgs):866 detected Vgs <>   
2005-09-21 16:24:46,153 INFO  libstorage - EvmsCo.cc(activate):966 old active:1   
val:1   
2005-09-21 16:24:46,153 INFO  libstorage - EvmsCo.cc(sendCommand):984 cmd:list   
fd:5   
   
   
Uninstalling yast2-storage-evms fixes this problem.  
Affected YaST modules are the software installation ("yast2 -i") and thus of  
course all YaST modules that call "yast2 -i" to install additional components.  
YOU is not affected.  
  
  
Summarizing a personal discussion (fehr + sh) there seems to be disagreement if 
this is a problem that needs to be addressed: yast2-storage-evms is not part of 
any software selection, so it is not installed by default or even by adding any 
software selections, but the package is there on the installation media, so 
users are free to select it for installation, even without any kind of warning. 
Thus it is a perfectly legal scenario for users to run into this problem. 
 
I consider this problem a showstopper for the great majority of all users - 
whoever will install this package will find many YaST modules unusable 
afterwards without any hint what happened or what to do to fix that problem. 
 
We should try to add some safety check to that package or to the respective 
function call to avoid that kind of hanging. If that is not possible, we need at 
least an installation notify message informing users who try to install that 
package.
Comment 1 Thomas Fehr 2005-09-21 14:38:11 UTC
Need y2log files.

I have not the slightest problem with yast2-storage-evms installed on
my system (of course it makes no sense and just increases yast2 startup
time considerably)
Comment 2 Stefan Hundhammer 2005-09-21 14:38:41 UTC
Created attachment 50542 [details]
y2logs.tgz
Comment 3 Stefan Hundhammer 2005-09-21 14:39:43 UTC
Created attachment 50543 [details]
hwinfo
Comment 4 Stefan Hundhammer 2005-09-21 14:40:17 UTC
fdisk -l 
 
Disk /dev/hda: 120.0 GB, 120034123776 bytes 
255 heads, 63 sectors/track, 14593 cylinders 
Units = cylinders of 16065 * 512 = 8225280 bytes 
 
   Device Boot      Start         End      Blocks   Id  System 
/dev/hda1               1         131     1052226   82  Linux swap / Solaris 
/dev/hda2             132        1437    10490445   83  Linux 
/dev/hda3            1438        2743    10490445   83  Linux 
/dev/hda4   *        2744       14592    95177092+  83  Linux 
 
Comment 5 Stefan Hundhammer 2005-09-21 15:05:15 UTC
Strange - can't reproduce after that one process was killed. 
We need to watch this. 
 
Decreasing severity. 
Comment 6 Thomas Fehr 2005-09-21 15:19:20 UTC
Strange, after killing the running evms_access process all was fine again and
the hanging processes were resumed. Afterwards it was not easily possible to
reproduce the hang. If it fail again please reopen and save the logfiles
from /var/log/YaST2 additionally useful might be "ipcs -a" and an strace
of the running evms_access process over a longer period of time.

JFI: for all normal SL 10.0 users, removal of yast2-storage-evms is an easy
workaround for this problem since EVMS handling is not present in YaST2 of
SL 10.0 anyway, so yast2-storage-evms just increases YaST2 startup time for
no good reason.
Comment 7 Thomas Fehr 2006-04-26 15:55:30 UTC
Should be fixed for SLES10 and SL 10.1
Comment 8 Bugzilla Account Maintenance 2008-09-02 18:08:09 UTC
Because the LATER and REMIND resolutions have been removed, the resolution of this bug has changed from REMIND to WONTFIX. If this bug needs to be reconsidered, reopen it and set a future "Target Milestone for Fix."