Bug 1559828 - [downstream clone - 4.1.10] "systemctl status lldpad.service" failed
Summary: [downstream clone - 4.1.10] "systemctl status lldpad.service" failed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhev-hypervisor-ng
Version: 4.1.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.10
: ---
Assignee: Yuval Turgeman
QA Contact: jiachen zhang
URL:
Whiteboard:
Depends On: 1555254
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-23 11:20 UTC by RHV bug bot
Modified: 2019-05-16 13:06 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1555254
Environment:
Last Closed: 2018-04-16 11:14:42 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1128 0 None None None 2018-04-16 11:14:56 UTC
oVirt gerrit 89212 0 master MERGED osupdater: also fix contexts on /dev 2018-03-23 11:21:13 UTC
oVirt gerrit 89349 0 ovirt-4.1 MERGED osupdater: also fix contexts on /dev 2018-03-23 11:21:13 UTC
oVirt gerrit 89350 0 ovirt-4.2 MERGED osupdater: also fix contexts on /dev 2018-03-23 11:21:13 UTC

Description RHV bug bot 2018-03-23 11:20:32 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1555254 +++
======================================================================

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....

(Originally by Jiachen Zhang)

Comment 1 RHV bug bot 2018-03-23 11:20:41 UTC
Consider this is a regression bug from RHVH 74 to RHVH 75.

(Originally by Chen Shao)

Comment 3 RHV bug bot 2018-03-23 11:20:45 UTC
How can this be a regression given https://bugzilla.redhat.com/show_bug.cgi?id=1555257 ?

(Originally by Ryan Barry)

Comment 5 RHV bug bot 2018-03-23 11:20:56 UTC
(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....

(Originally by Chen Shao)

Comment 8 jiachen zhang 2018-04-03 10:11:23 UTC
I tested this bug with these version: 
redhat-virtualization-host-4.1-20180329.0
redhat-release-virtualization-host-4.1-10.4.el7.x86_64 
imgbased-0.9.56-0.1.el7ev.noarch. 

However, the lldpad.service is still failed. I want to know whether this problem has been fixed?

Comment 9 Ryan Barry 2018-04-03 10:50:35 UTC
There was a patch for this in the last build, but the service may not have been enabled -- swapping back to 7.5 required some juggling of the release file

Can you post the status of audit2allow -a and systemctl status imgbase-relabel-dev.service?

Comment 10 Ryan Barry 2018-04-03 12:11:38 UTC
I double-checked this, and the service was not enabled when we swapped back to 7.5. It will be enabled in the next 7.5 build

Comment 11 jiachen zhang 2018-04-04 07:05:51 UTC
I test the bug with the version: redhat-virtualization-host-4.1-20180403.1
and the lldpad.service is active(running) after I add rhvh to rhvm. So the bug has been fixed successfully. I will changed the status to VERIFIED.

Comment 14 errata-xmlrpc 2018-04-16 11:14:42 UTC
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/RHBA-2018:1128

Comment 15 Franta Kust 2019-05-16 13:03:55 UTC
BZ<2>Jira Resync


Note You need to log in before you can comment on or make changes to this bug.