-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-9.2.0
-
lldpad-1.1.1-1.gitf1dd9eb.el9
-
None
-
Moderate
-
rhel-net-core
-
ssg_networking
-
4
-
11
-
3
-
False
-
False
-
-
None
-
None
-
If docs needed, set a value
-
-
Unspecified
-
None
-
57,005
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:
- is cloned by
-
RHEL-61874 Configuration can't be saved after lldpad terminated
-
- Closed
-
- external trackers
- links to
-
RHBA-2024:139712 lldpad update