Hide Forgot
Description of problem: When specifying storage_init=/dev/vd* (for example) and firstboot, the dracut plugin will wipe all disks that match /dev/vd*. In other situations, storage_init=/dev/vd* will resolve to the first match (/dev/vda). The dracut plugin should do the same resolving Version-Release number of selected component (if applicable): 6.2-0.9 How reproducible: Always Steps to Reproduce: 1. Have a machine with multiple disks (vm with /dev/vda /dev/vdb) 2. run rhevh with storage_init=/dev/vd* firstboot 3. Actual results: dracut plugin will report that it wiped /dev/vda, /dev/vda1.. (for all partitions) and /dev/vdb and all partitions ( and vdc... if you have them) Expected results: should resolve /dev/vd* to be first matching disk (/dev/vda) Additional info: Also need to watch out for multiple disks, e.g. /dev/vd*,/dev/vdb
Issue actually comes up when specifying multiple disks, not just a single disk. storage_init=/dev/vd*,/dev/vdc
Created attachment 519285 [details] Patch Patch simply escapes wildcards prior to the for loop, and removes escaping once in the for loop: For testing: various combinations of storage_init parameter including * /dev/vd*,/dev/vdb For verifying, if you pass rdinfo on the kernel command line, you'll get output like: dracut: checking device "/dev/vd*" for all device checked. The lines should match exactly what was passed in the storage_init parameter
Created attachment 519295 [details] Patch Previous patch file was for a different bz
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1783.html