Red Hat Bugzilla – Bug 239407
usb-storage changes device order post installation
Last modified: 2012-05-19 19:50:13 EDT
Description of problem: When carrying out an installation using a usb-storage device (for e.g. USB floppy) the device node assigned to the device changes between the installation environment and the installed system. E.g.: During installation: HDD -> /dev/sda, FDD -> /dev/sdb After installation: HDD -> /dev/sdb, FDD -> /dev/sda This is related to bug 234815. Version-Release number of selected component (if applicable): 10.1.1.46 How reproducible: 100% Steps to Reproduce: 1. Carry out an installation with a usb-storage device attached, e.g. kickstart from USB floppy 2. Check device node assignment during installation 3. Check device node assignment after installation Actual results: Device nodes are exchanged between the installer and installed environments. Expected results: Device nodes remain unchanged between the installer and installed environments. Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
requested by Jams Antill
Moving to 4.7.
Yes, lack of engineering capacity. The device enumeration process works much better in RHEL5 than 4 and I don't view this as that critical of a problem. Worst case, we can document it in the release notes and make sure customers are aware of what can potentially happen when USB devices are connected during installation.
See comment #8. The amount of work this would require, combined with the fact that this isn't really breaking anything, makes this a poor candidate for an update so late in the RHEL4 product life cycle. This does seem like a good candidate for a release note.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
*** This bug has been marked as a duplicate of 248619 ***