Bug 1821385

Summary: Failed to start nova_virtlogd healthcheck after deployment
Product: Red Hat OpenStack Reporter: David Rosenfeld <drosenfe>
Component: openstack-tripleo-commonAssignee: Rajesh Tailor <ratailor>
Status: CLOSED ERRATA QA Contact: David Rosenfeld <drosenfe>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: amodi, aschultz, bdobreli, lyarwood, mburns, pbabbar, pweeks, slinaber, smooney
Target Milestone: betaKeywords: Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-common-11.3.3-0.20200606003438.e567172.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-29 07:51:29 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 David Rosenfeld 2020-04-06 17:42:18 UTC
Description of problem: After each deployment job the overcloud podman healthcheck test is failing with this error:

assert not {'192.168.24.11': {'tripleo_nova_virtlogd_healthcheck.service': "● tripleo_nova_virtlogd_healthcheck.service - nova_vi...e: Failed with result 'exit-code'.\nApr 04 23:43:18 compute-0 systemd[1]: Failed to start nova_virtlogd healthcheck."}}

Script checks healthchecks with this command:
sudo systemctl list-units --failed --plain --no-legend --no-pager |grep "healthcheck.service" |awk '{print $1}' | sort


Version-Release number of selected component (if applicable): RHOS_TRUNK-16.1-RHEL-8-20200404.n.0


How reproducible: Every time a jenkins deployment job has been executed.

Steps to Reproduce:
1. Execute a deployment job e.g.: DFG-df-deployment-16.1-virthost-1cont_1comp_3ceph-no_UC_SSL-no_OC_SSL-ceph-ipv4-geneve-RHELOSP-31811
2.
3.

Actual results: Failed to start nova_virtlogd healthcheck


Expected results: nova_virtlogd healthcheck starts


Additional info:

Comment 16 errata-xmlrpc 2020-07-29 07:51:29 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-2020:3148