Bug 2138970

Summary:	Setting adminStatus=disabled does not survive reboot
Product:	Red Hat Enterprise Linux 9	Reporter:	Matt Lucius <malucius>
Component:	lldpad	Assignee:	Aaron Conole <aconole>
Status:	CLOSED MIGRATED	QA Contact:	Matt Lucius <malucius>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	kzhang
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-21 10:54:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Matt Lucius 2022-10-31 19:52:51 UTC

Description of problem:
This is a follow-on to BZ1997064 (same summar). The fix for the original problem went into the 1.0.1-19 build of lldpad, but it needs to get rolled into lldpad 1.1.0, which is what RHEL 9.2 is using.

Aaron Conole made the fix in RHEL 8 and knows this bug is coming.

Version-Release number of selected component (if applicable):
lldpad-1.1.0-4.git85e5583.el9

How reproducible:
Always

Steps to Reproduce:
1. Configure several virtual interfaces to be created at boot time
2. Start lldpad
3. lldptool set-lldp -i <interface> adminStatus=rxtx #assume it starts as "disabled"
4. reboot
5. start lldpad
6. lldptool get-lldp -i <interface> adminStatus
7. Observe: adminstatus=rxtx
8. lldptool set-lldp -i <interface> adminStatus=disabled
9. modify order of virtual interface creation
10. reboot
11. start lldpad
12. lldptool get-lldp -i <interface> adminStatus
13. Observe: adminstatus=rxtx

Actual results:
adminStatus reverts to rxtx

Expected results:
adminStatus should maintain "disabled."

Additional info:

Comment 1 RHEL Program Management 2023-09-21 10:50:45 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-21 10:54:31 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.