Bug 734374
Summary: | boot from SAN will got different mount point with mpath name. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Gris Ge <fge> |
Component: | anaconda | Assignee: | Ales Kozumplik <akozumpl> |
Status: | CLOSED ERRATA | QA Contact: | Gris Ge <fge> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1 | CC: | akozumpl, jzeleny |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | anaconda-13.21.139-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 10:41:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 743047 |
Description
Gris Ge
2011-08-30 09:02:57 UTC
Hi, can you please retest with updates=http://akozumpl.fedorapeople.org/bz734374.img ? Thanks, Ales Hi, can you please retest with updates=http://akozumpl.fedorapeople.org/bz734374.img ? Thanks, Ales Ales, I don't have physical access to that server, can we have a repo and network-install boot initrd? (In reply to comment #3) > Ales, > > I don't have physical access to that server, can we have a repo and > network-install boot initrd? You don't need physical access, it is an updates image. This is how you use an updates image: http://fedoraproject.org/wiki/Anaconda/Updates Alex, Sorry for the misunderstanding. Add "updates=http://akozumpl.fedorapeople.org/bz734374.img" into beaker "Kernel Options" fit the needed. Beaker job: https://beaker.engineering.redhat.com/jobs/126257 It test 4 senario: 1. ondisk=/dev/disk/by-id/dm-uuid-mpath-WWID 2. ignoredisk --only-use=disk/by-id/scsi-WWID (typo in beaker whiteboard) 3. ondisk=mpatha 4. ignoredisk --only-use=mpatha All of them are using mpath[a-z] for mpath name. So, you create "/etc/multipath/bindings" for all conditions? (In reply to comment #5) > All of them are using mpath[a-z] for mpath name. > > So, you create "/etc/multipath/bindings" for all conditions? No, only in cases where friendly names are used. But the way to disable friendly names is through UI and is not done simply by using the /by-id/ paths in kickstart. This is the expected behavior. Ales Patch posted for review: https://www.redhat.com/archives/anaconda-devel-list/2011-September/msg00031.html Any kickstart option I could use to disable friendly names? (In reply to comment #8) > Any kickstart option I could use to disable friendly names? Nope. Fixed: 445ca8d757c1b388894b46cb22b9646c3a3535ee (rhel6-branch) ea4a92ce4fd850f77806534153140c3602d2edfe (master) Ales, I cannot find any GUI option for disable "friendly names" on repo: RHEL6.2-20110907.1 It might be in "advanced storage" setting page, but that page got skiped when installing on "boot from SAN". Am I missed anything? It seems repo RHEL6.2-20110907.1 don't have this patch applied: https://beaker.engineering.redhat.com/jobs/133061 I will wait for next repo. (In reply to comment #13) > Ales, > > I cannot find any GUI option for disable "friendly names" on repo: > RHEL6.2-20110907.1 > > It might be in "advanced storage" setting page, but that page got skiped when > installing on "boot from SAN". > > Am I missed anything? The only way to disable friendly names is to enter the "Specialized Storage Devices" page and click "Device Options". Repo: RHEL6.2-20110919.n.0 have this fix. Will perform the detailed test after other regression test. GUI options works as expected. https://beaker.engineering.redhat.com/jobs/135879 Beaker job confirmed following options works well also: 1. ondisk=/dev/disk/by-id/dm-uuid-mpath-<WWID> #without LVM 2. ignoredisk --only-use=disk/by-id/scsi-<WWID> #with LVM 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-1565.html |