Red Hat Bugzilla – Bug 1555254
"systemctl status lldpad.service" failed
Last modified: 2018-05-15 13:58:59 EDT
Created attachment 1407890 [details] /var/log /tmp Description of problem: After running the command "systemctl status lldpad.service", the service status is failed. Version-Release number of selected component (if applicable): RHVH-4.1-20180307.1-RHVH-x86_64-dvd1.iso How reproducible: 100% Steps to Reproduce: 1. Install RHVH-4.1-20180307.1-RHVH-x86_64-dvd1.iso, configure network successful. 2. Add RHVH to RHEV-M. 3. Check the service use "systemctl status lldpad.service". Actual results: 1. After step 3, lldpad.service is failed. Expected results: 1. After step 3, lldpad.service is active. Additional info: [root@dell-per730-34 ~]# systemctl status lldpad.service ● lldpad.service - Link Layer Discovery Protocol Agent Daemon. Loaded: loaded (/usr/lib/systemd/system/lldpad.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-03-14 16:47:01 CST; 15min ago Process: 19388 ExecStart=/usr/sbin/lldpad -t (code=exited, status=1/FAILURE) Main PID: 19388 (code=exited, status=1/FAILURE) Mar 14 16:47:01 dell-per730-34.lab.eng.pek2.redhat.com systemd[1]: Started Link Layer Discovery Protocol..... Mar 14 16:47:01 dell-per730-34.lab.eng.pek2.redhat.com systemd[1]: Starting Link Layer Discovery Protoco..... Mar 14 16:47:01 dell-per730-34.lab.eng.pek2.redhat.com lldpad[19388]: error getting shm pid Mar 14 16:47:01 dell-per730-34.lab.eng.pek2.redhat.com systemd[1]: lldpad.service: main process exited, ...RE Mar 14 16:47:01 dell-per730-34.lab.eng.pek2.redhat.com systemd[1]: Unit lldpad.service entered failed state. Mar 14 16:47:01 dell-per730-34.lab.eng.pek2.redhat.com systemd[1]: lldpad.service failed. No such issue on redhat-virtualization-host-4.1-20180313.0 (based on 74) # imgbase w You are on rhvh-4.1-0.20180313.0+1 [root@localhost /]# systemctl status lldpad.service ● lldpad.service - Link Layer Discovery Protocol Agent Daemon. Loaded: loaded (/usr/lib/systemd/system/lldpad.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-03-14 04:13:55 EDT; 59min ago Main PID: 29746 (lldpad) CGroup: /system.slice/lldpad.service └─29746 /usr/sbin/lldpad -t Mar 14 04:13:55 localhost.localdomain systemd[1]: Started Link Layer Discovery Protocol Agent Daemon.. Mar 14 04:13:55 localhost.localdomain systemd[1]: Starting Link Layer Discovery Protocol Agent Daemon....
Consider this is a regression bug from RHVH 74 to RHVH 75.
How can this be a regression given https://bugzilla.redhat.com/show_bug.cgi?id=1555257 ?
(In reply to Ryan Barry from comment #2) > How can this be a regression given > https://bugzilla.redhat.com/show_bug.cgi?id=1555257 ? Try to test on previous version redhat-virtualization-host-4.1-20180126.0 (4.1.9 ASYNC), can't reproduce this issue, so give regression keywords. # imgbase w You are on rhvh-4.1-0.20180126.0+1 # # systemctl status lldpad.service ● lldpad.service - Link Layer Discovery Protocol Agent Daemon. Loaded: loaded (/usr/lib/systemd/system/lldpad.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-03-14 23:21:45 EDT; 1min 2s ago Main PID: 1556 (lldpad) CGroup: /system.slice/lldpad.service └─1556 /usr/sbin/lldpad -t Mar 14 23:21:45 dhcp-8-111.nay.redhat.com systemd[1]: Started Link Layer Discovery Protocol Agent Daemon.. Mar 14 23:21:45 dhcp-8-111.nay.redhat.com systemd[1]: Starting Link Layer Discovery Protocol Agent Daemon....
Test this bug with RHVH-4.2-20180410.1 After added RHVH to RHEVM, lldpad.service is active. So it has been fixed successfully.
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/RHSA-2018:1524