Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
In RHEL7 it was possible to set adminStatus=disasbled for interface
and this status was persisted across reboot.
Version-Release number of selected component (if applicable):
lldpad-1.0.1-14.git036e314.el8.x86_64.
How reproducible:
100%
Steps to Reproduce:
1. lldptool set-lldp –i $INTERFACE adminStatus=disabled
2. Reboot
3. lldptool get-lldp -i $INTERFACE adminStatus
Actual results:
Returns: "rx" or "rxtx"
Expected results:
Returns: "disabled"
I see what is happened now.
The ifindex is changing on the system, and this interacts negatively with:
e272d34f45bc ("Use interface index instead of name in libconfig")
For example, I have a system where I booted it a few times, and got different ifindex on
some of the hardware because of PCI delays, etc.
So it seems this patch has some issues. I have commented on:
https://github.com/intel/openlldp/pull/3
And will work with upstream on it.
(In reply to Aaron Conole from comment #2)
>
> And will work with upstream on it.
So what is the status on an upstream fix?
The 1.0.1-16 has a fix for the nl socket buffer segfault, but the issue associated with a non-stable index.
Here is some justification and another example.
A couple of struggles with the Marvell Qlogic driver in Virt configurations where we would drop frames and lose paths seems to now be understood.
The new out of box driver that was provided for some scatter/gather fixes in the driver and firmware disables priority flow control if lldpad is enabled on boot.
The problem is vdsm in RHV will keep starting even if it is set to disabled, so we need to remove the vdsm dependency on lldpad.
The lldpad service is only needed for software based FCOE, not the Marvell full offload qedf adapters so now with these new driver changes is going break stuff for customers with the ubiquitous qedf Fastlinq adapters in HPE servers.
Note that the inbox drivers in 8.5 for example dont break even with lldpad enabled and that is how this has escaped us for so long.
It is the new Marvell F/W and driver changes that see this new issue.
So we need a BZ created for the correct team in RHEV/Virt ENG to get this resolved please.
If you create the BZ ping me and I will provide a technical update.
Thanks
Laurence
Trying to reproduce the issue against lldpad 1.0.1-14 with a variety of boards setting lldpad to start on boot, then following the "set, reboot, get" sequence described above. I'm not able to see the issue with any type of NIC so far. Are there any which are more likely to have the problem?
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 (lldpad bug fix and enhancement update), 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-2022:7807