Hide Forgot
Created attachment 1210447 [details] anaconda.log Description of problem: LVMError: lvactivate failed for swap: running lvm lvchange -a y rhel_storageqe-54/swap --config devices { preferred_names=["^/dev/mapper/", "^/dev/md/", "^/dev/sd"] filter=["r|/sdi1$|","r|/sdi2$|","r|/sdj1$|","r|/sda1$|","r|/sda2$|","r|/sda4$|","r|/vg01-lv01$|","r|/vg01$|","r|/sda5$|","r|/sda6$|","r|/sda7$|","r|/sda$|","r|/360a9800042566643352b476d67496e58p1$|","r|/360a9800042566643352b476d67496e58$|","r|/sdc$|","r|/360a9800042566643352b476d67496e5a1$|","r|/360a9800042566643352b476d67496e5a2$|","r|/360a9800042566643352b476d67496e5a$|","r|/sdd$|","r|/360a9800042566643352b476d67496e61p1$|","r|/360a9800042566643352b476d67496e61$|","r|/sde$|","r|/360a9800042566643352b476d67497675$|","r|/sdf$|","r|/sdh$|","r|/sdi$|","r|/sdj$|","r|/sdk$|"] } failed Version-Release number of selected component (if applicable): RHEL-7.3-20161012.0 Server x86_64 anaconda 21.48.22.93-1 How reproducible: always Steps to Reproduce: 1. Install all system on the FCoE disk 2. Select the automatically partition 3. Issue is happened Actual results: Installation is aborted Expected results: Installation can be finished successfully Additional info:
Created attachment 1210448 [details] anaconda-tb-NMVV8l
Created attachment 1210452 [details] storage.log
Created attachment 1210453 [details] console.log
Above server is storageqe-54, job is https://beaker.engineering.redhat.com/jobs/1552710 The same issue occurs on other SAN boot server st60 when I install it by manual: storageqe-60 https://beaker.engineering.redhat.com/jobs/1552712
On the same server, it worked on RHEL-7.3 Snapshot 5. storageqe-60 manual PASS https://beaker.engineering.redhat.com/jobs/1524853
Compared the anaconda version, they are different in the pass and fail jobs: anaconda-21.48.22.92-1 PASS https://beaker.engineering.redhat.com/jobs/1524853 anaconda-21.48.22.93-1 FAIL https://beaker.engineering.redhat.com/jobs/1552712
There were no storage related changes in anaconda or blivet after Snapshot 5.
The workaround mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1378714#c41 works to me.
(In reply to xhe from comment #9) > The workaround mentioned in > https://bugzilla.redhat.com/show_bug.cgi?id=1378714#c41 works to me. Thanks for the note -- in this case, I'm going to duplicate this to bug 1378714 since the issue also looks the same. *** This bug has been marked as a duplicate of bug 1378714 ***