Bug 2138970 - Setting adminStatus=disabled does not survive reboot
Summary: Setting adminStatus=disabled does not survive reboot
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: lldpad
Version: 9.2
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Aaron Conole
QA Contact: Matt Lucius
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-31 19:52 UTC by Matt Lucius
Modified: 2023-07-27 09:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1997064 0 unspecified CLOSED Setting adminStatus=disabled does not survive reboot 2023-05-22 12:17:21 UTC
Red Hat Issue Tracker RHELPLAN-137931 0 None None None 2022-10-31 19:56:23 UTC

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:
Note You need to log in before you can comment on or make changes to this bug.