Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1814130

Summary: [RHOSP13]neutron container are in unhealthy state after deployment.
Product: Red Hat OpenStack Reporter: MD Sufiyan <msufiyan>
Component: openstack-tripleo-commonAssignee: Adriano Petrich <apetrich>
Status: CLOSED DUPLICATE QA Contact: David Rosenfeld <drosenfe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: aschultz, bcafarel, jlibosva, mburns, rrubins, slinaber, srelf, vz.mec
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-19 12:26:01 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:

Comment 2 Steve Relf 2020-03-18 20:58:26 UTC 
currently affecting me as well.

running computes
openstack-neutron-openvswitch-agent:13.0-114

Controller
3d9379ca71a0        10.42.36.7:8787/rhosp13/openstack-neutron-openvswitch-agent:13.0-114    "dumb-init --singl..."   4 days ago          Up 7 hours (unhealthy)                       neutron_ovs_agent
d328af17087b        10.42.36.7:8787/rhosp13/openstack-neutron-l3-agent:13.0-113             "dumb-init --singl..."   4 days ago          Up 7 hours (unhealthy)                       neutron_l3_agent
769dd2a63a11        10.42.36.7:8787/rhosp13/openstack-neutron-metadata-agent:13.0-115       "dumb-init --singl..."   4 days ago          Up 7 hours (unhealthy)                       neutron_metadata_agent
f07118b0a6fd        10.42.36.7:8787/rhosp13/openstack-neutron-dhcp-agent:13.0-114           "dumb-init --singl..."   4 days ago          Up 7 hours (unhealthy)                       neutron_dhcp

Doenst seem to affect the operation of the cloud though.
Comment 3 Bernard Cafarelli 2020-03-19 12:26:01 UTC 

*** This bug has been marked as a duplicate of bug 1813758 ***