Bug 1636254
| Summary: | disable lldp in vdsm to avoid FCoE storage not initiated on boot | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Koutuk Shukla <kshukla> | ||||
| Component: | vdsm | Assignee: | Dominik Holler <dholler> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | high | Docs Contact: | Rolfe Dlugy-Hegwer <rdlugyhe> | ||||
| Priority: | medium | ||||||
| Version: | 4.2.6 | CC: | bugs, danken, dholler, dougsland, ebenahar, eshenitz, gveitmic, kshukla, lsurette, mavital, mburman, mkalinin, mkeir, mtessun, rbarry, rdlugyhe, srevivo, tnisan, ycui, yturgema | ||||
| Target Milestone: | ovirt-4.3.0 | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||
| Doc Text: |
VDSM uses lldpad. Due to a bug, lldpad confuses NetXtreme II BCM57810 FCoE-enabled cards. When the VDSM configuration enables lldpad to read lldp data from the card, it renders the card unusable. To work around this issue, set enable_lldp=false in vdsm.conf.d and restart VDSM. Check that lldpad is disabled on all relevant interfaces by entering the command, "lldptool get-lldp -i $ifname adminStatus". If lldp is enabled, disable it by entering "lldptool set-lldp -i $ifname adminStatus=disabled". After ensuring that lldp support is disabled in VDSM, networking should be unaffected.
|
Story Points: | --- | ||||
| Clone Of: | 1551403 | Environment: | |||||
| Last Closed: | 2019-05-08 12:36:02 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1551403, 1623904 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Koutuk Shukla
2018-10-04 20:44:56 UTC
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops
Hi Dominik, Michael, My concern with this bug is that customer has reported that service network restart was required after the manual config and host reboot: "On a network restart I now see both FCoE working correctly. However, it still doesn't work automatically on reboot." We need to confirm the fix in the bug is sufficient and would not require network restart. And if it does, we need to provide some script to the customer to make it happening automatically[1] or fix it in the code. [1] Maybe we can create a systemd unit that will to the network restart before vdsmd starts? Or there is a better solution you can recommend? https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sect-managing_services_with_systemd-unit_files This runs the risk of a system dependency loop vdsmd->vdsm-network->vdsm-init-network->openvswitch.service && network.target The best explanation for this not working until the network service is restarted is that some other service makes a change once network is up. Probably lldpad. The best solution in this case is working around the problem service, either through blacklisting as Dominik suggested or by requesting a change in service ordering from platform. IMO, service startup on a clean reboot should be idiomatic and not require re-starting a service which has been up for less than 5 seconds in order to achieve the desired results. WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:
[Found non-acked flags: '{'rhevm-4.3-ga': '?'}', ]
For more info please contact: rhv-devops
Created attachment 1521303 [details]
validation that disableing lldp on the interface resolves the initial problem
Michael, from my point of view attachment 1521303 [details] shows the validation for this bug. Do you agree?
(In reply to Dominik Holler from comment #28) > Michael, from my point of view attachment 1521303 [details] shows the > validation for this bug. Do you agree? Yes. Dominik, can you set the bug to ON_QA please? Verified on vdsm-4.20.46-1.el7ev.x86_64 and vdsm-4.30.6-1.el7ev.x86_64 Hi Dominik. Please verify the updated content in the Doc Text field (above). Thank you. (In reply to Rolfe Dlugy-Hegwer from comment #32) > Hi Dominik. Please verify the updated content in the Doc Text field (above). > Thank you. Doc Text sounds good, thanks. 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. https://access.redhat.com/errata/RHBA-2019:1077 |