Hide Forgot
Description of problem: After FCOE installations, the resulting initrd does not set AUTO_VLAN for the associated NIC. How reproducible: 100% Steps to Reproduce: 1. Install over FCOE with a target whcih is visible on a VLAN 2. Reboot 3. Actual results: No LUNs are visible from dracut, and the system is not bootable Expected results: Everything works. Additional info: I don't really have much experience with FCOE, so I might be way off here - But 2 things I noticed on that machine that might be worth something: 1. AUTO_VLAN in the initrd (/etc/fcoe/cfg-p5p1) is set to "no" and `fcoeadm -i` shows p5p1 as Offline. 2. Running `fipvlan -dcs p5p1` in initrd will start fcoe, and now fcoeadm will show p5p1 as Online and display a bunch of luns there as well. After this, running lvm_scan will show all the missing lvs under /dev/rhvh_dell-per730-35/
Please attach - installer logs (/var/log/anaconda/* in the installed system) - the kickstart file if there was used any - the content of /etc/fcoe/cfg-* files from initrd and installed system root.
Chen, can you provide these? I don't have an FCOE environment to test with
Created attachment 1434166 [details] all log
(In reply to Ryan Barry from comment #3) > Chen, can you provide these? I don't have an FCOE environment to test with Sure, already uploaded all log info.
Created attachment 1434167 [details] /etc/fcoe/* after reboot
(In reply to cshao from comment #6) > Created attachment 1434167 [details] > /etc/fcoe/* after reboot I think the value (cfg file) is set by dracut, probably here: https://github.com/dracutdevs/dracut/blob/RHEL-7/modules.d/95fcoe/fcoe-up.sh#L94 Anaconda is not passing vlan value to dracut as there is no option to do that, and it seems the value is inferred from other values and drivers used. Related patch: https://github.com/dracutdevs/dracut/commit/d02f522089863af2a802cef9e63965349bfcc819
Asking Chris for ideas.
After you install the machine can you add rd.debug to kernel cmdline and after the boots times out get the rdsosreport.txt and put it here?
(In reply to Lukáš Nykrýn from comment #9) > After you install the machine can you add rd.debug to kernel cmdline and > after the boots times out get the rdsosreport.txt and put it here? Already send test env to you by mail.
I think we need to backport https://github.com/dracutdevs/dracut/commit/2aac3194100b903740bb9057aed71a35ce92a2e3 , but I would like to have Chris' opinion on that.
(In reply to Lukáš Nykrýn from comment #11) > I think we need to backport > https://github.com/dracutdevs/dracut/commit/ > 2aac3194100b903740bb9057aed71a35ce92a2e3 , but I would like to have Chris' > opinion on that. That seems reasonable, as switches should reply to VLAN discovery with an ID of 0 and fcoemon looks to enable FCoE on the base interface in that case. I'm trying to think of where we might run into switches that don't do VLAN discovery at all, and the only place I'm worried about is really old Cisco UCS fnic setups. And I'm not sure there's going to be an issue there.
Please consider to backport this to 7.5
(In reply to Sandro Bonazzola from comment #13) > Please consider to backport this to 7.5 I am not 100% confident that the patch can't break anything and given the limited testing during z-stream I don't think it should go there. Also, we don't respin the installation images, so the fix might not be that useful in the end
(In reply to Lukáš Nykrýn from comment #14) > (In reply to Sandro Bonazzola from comment #13) > > Please consider to backport this to 7.5 > > I am not 100% confident that the patch can't break anything and given the > limited testing during z-stream I don't think it should go there. Also, we > don't respin the installation images, so the fix might not be that useful in > the end Any update on this for 7.6?
Samantha?
Missed 7.6, retrying with 7.6.z
Missed 7.7, retrying with 8.1 for RHV 4.4
Any update?
Looka we should be able to backport this for 8.2.
Hmm, it looks we already have this patch in rhel. So I have no idea what to do here.
Chris any ideas?
Hi, any updates on this issue? We are following a similar case and every hint can be really helpful.
Chen, is this still reproducible with RHV-4.4 based on RHEL 8.2?
(In reply to Sandro Bonazzola from comment #27) > Chen, is this still reproducible with RHV-4.4 based on RHEL 8.2? Working on this now, will update later.
(In reply to Sandro Bonazzola from comment #27) > Chen, is this still reproducible with RHV-4.4 based on RHEL 8.2? Test version: redhat-virtualization-host-4.4.0-20200318.0.el8_2 fcoe-utils-1.0.32-7.el8.x86_64 imgbased-1.2.8-1.el8ev.noarch RHVH can't detect FCOE storage at all. 1. Install RHVH-UNSIGNED-ISO-4.4-RHEL-8-20200318.0-RHVH-x86_64-dvd1.iso via anaconda GUI on FCoE storage machine. 2. Specialized & Network disks -> Add a disk -> Add FCoE SAN -> NIC(p5p1/p5p2) -> choose "use auto Vlan" Test result: RHVH can't detect FCOE storage at all.
Thank you for testing it, Chen. In previuos comments, it was clear that the above mentioned patches were already applied in RHEL. Could it be useful to pass the fcoe boot argument to dracut to be totally sure that the desired interface has been used? The boot argument is: fcoe=<edd|interface|MAC>:{dcb|nodcb}:{fabric|vn2vn} Mac addresses must be lowercase.
Not blocking RHV 4.4 on this bug but still important for RHV.
(In reply to cshao from comment #32) > Any update? can you please try again with suggestion from comment #30?
(In reply to Gianni Salinetti from comment #30) > Thank you for testing it, Chen. > > In previuos comments, it was clear that the above mentioned patches were > already applied in RHEL. > > Could it be useful to pass the fcoe boot argument to dracut to be totally > sure that the desired interface has been used? > > The boot argument is: > fcoe=<edd|interface|MAC>:{dcb|nodcb}:{fabric|vn2vn} > > Mac addresses must be lowercase. Test version: RHVH-4.4-20200618.0-RHVH-x86_64-dvd1.iso RHVH can't detect FCOE storage at all. 1. pass below fcoe boot argument to dract: fcoe=<edd|enp7sofo|a0:36:9f:ae:9f:50>:{dcb|nodcb}:{fabric|vn2vn} 1. Install RHVH-4.4-20200618.0-RHVH-x86_64-dvd1.iso via anaconda GUI on FCoE storage machine. 2. Specialized & Network disks -> Add a disk -> Add FCoE SAN -> NIC(enp7sofo) -> choose "use auto Vlan" Test result: RHVH can't detect FCOE storage at all.
(In reply to cshao from comment #34) > (In reply to Gianni Salinetti from comment #30) > > Thank you for testing it, Chen. > > > > In previuos comments, it was clear that the above mentioned patches were > > already applied in RHEL. > > > > Could it be useful to pass the fcoe boot argument to dracut to be totally > > sure that the desired interface has been used? > > > > The boot argument is: > > fcoe=<edd|interface|MAC>:{dcb|nodcb}:{fabric|vn2vn} > > > > Mac addresses must be lowercase. > > > > Test version: > RHVH-4.4-20200618.0-RHVH-x86_64-dvd1.iso > > > RHVH can't detect FCOE storage at all. > 1. pass below fcoe boot argument to dract: > fcoe=<edd|enp7sofo|a0:36:9f:ae:9f:50>:{dcb|nodcb}:{fabric|vn2vn} > 1. Install RHVH-4.4-20200618.0-RHVH-x86_64-dvd1.iso via anaconda GUI on FCoE > storage machine. > 2. Specialized & Network disks > -> Add a disk > -> Add FCoE SAN > -> NIC(enp7sofo) > -> choose "use auto Vlan" > > Test result: > RHVH can't detect FCOE storage at all. Are any error/warning messages shown?
(In reply to David Tardon from comment #36) > (In reply to cshao from comment #34) > > (In reply to Gianni Salinetti from comment #30) > > > Thank you for testing it, Chen. > > > > > > In previuos comments, it was clear that the above mentioned patches were > > > already applied in RHEL. > > > > > > Could it be useful to pass the fcoe boot argument to dracut to be totally > > > sure that the desired interface has been used? > > > > > > The boot argument is: > > > fcoe=<edd|interface|MAC>:{dcb|nodcb}:{fabric|vn2vn} > > > > > > Mac addresses must be lowercase. > > > > > > > > Test version: > > RHVH-4.4-20200618.0-RHVH-x86_64-dvd1.iso > > > > > > RHVH can't detect FCOE storage at all. > > 1. pass below fcoe boot argument to dract: > > fcoe=<edd|enp7sofo|a0:36:9f:ae:9f:50>:{dcb|nodcb}:{fabric|vn2vn} > > 1. Install RHVH-4.4-20200618.0-RHVH-x86_64-dvd1.iso via anaconda GUI on FCoE > > storage machine. > > 2. Specialized & Network disks > > -> Add a disk > > -> Add FCoE SAN > > -> NIC(enp7sofo) > > -> choose "use auto Vlan" > > > > Test result: > > RHVH can't detect FCOE storage at all. > > Are any error/warning messages shown? There is no message pop-up in anaconda GUI.
(In reply to cshao from comment #37) > There is no message pop-up in anaconda GUI. And on console? https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_installation/installer-troubleshooting_installing-rhel#consoles-logging-during-install_troubleshooting-at-the-start-of-the-installation
(In reply to David Tardon from comment #38) > (In reply to cshao from comment #37) > > There is no message pop-up in anaconda GUI. > > And on console? > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ > html/performing_a_standard_rhel_installation/installer- > troubleshooting_installing-rhel#consoles-logging-during- > install_troubleshooting-at-the-start-of-the-installation Will try to provide console log ASAP.
Created attachment 1731133 [details] fcoe log
(In reply to David Tardon from comment #38) > (In reply to cshao from comment #37) > > There is no message pop-up in anaconda GUI. > > And on console? > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ > html/performing_a_standard_rhel_installation/installer- > troubleshooting_installing-rhel#consoles-logging-during- > install_troubleshooting-at-the-start-of-the-installation Please refer "fcoe log" for more info.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.