RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (
issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the
Red Hat customer portal. If you're not, please head to the "
RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "
NEW", "
ASSIGNED", and "
POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "
kernel", "
kernel-rt", and "
kpatch" are only migrated if still in "
NEW" or "
ASSIGNED". If you cannot log in to RH Jira, please consult
article #7032570. That failing, please send an e-mail to the RH Jira admins at
rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "
CLOSED", resolution "
MIGRATED", and set with "
MigratedToJIRA" in "
Keywords". The link to the successor Jira issue will be found under "
Links", have a little "two-footprint" icon next to it, and direct you to the "
RHEL project" in Red Hat Jira (issue links are of type "
https://issues.redhat.com/browse/RHEL-XXXX", where "
X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 490370 [details] dmesg boot log Description of problem: I'm seeing sda become sdb when I move from kernel-2.6.32-125.el6.x86_6 to kernel-2.6.32-128.el6.x86_64 on veritas[2,3].rhts.eng.bos.redhat.com. Version-Release number of selected component (if applicable): kernel-2.6.32-128.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Install snapshot-1 2. Boot the system and look at /proc/partitions 3. Install kernel-2.6.32-128.el6.x86_64 and reboot 4. Check /proc/partitions again. Or 1. Install snapshot-2 directly and check /proc/partitions. Actual results: With kernel-2.6.32-128.el6.x86_64 the megaraid boot device ends up being labeled sdb. On all previous kernels I've tested it is sda. Expected results: Additional info: