Description of problem: Following neutron containers are marked unhealthy after updating to RHOSP 13 Z11: - neutron_ovs_agent - neutron_l3_agent - neutron_metadata_agent - neutron_dhcp The healthcheck should fail if there are no open connections from proper neutron daemon to rabbitmq [1]. healthcheck will grep through "ss -ntp" output obtained from docker container to select specific ports and process. For neutron containers the following process names will be used: - neutron_ovs_agent: neutron-openvswitch-agent - neutron_l3_agent: neutron-l3-agent - neutron_metadata_agent: neutron-metadata-agent - neutron_dhcp: neutron-dhcp-agent Before RHOSP 13 Z11 you will get the following outputs for neutron_metadata_agent container (note "neutron-metadat" process): # docker exec -it neutron_metadata_agent ss -ntp | grep neutron-meta ESTAB 0 0 172.17.1.10:45298 172.17.1.10:5672 users:(("neutron-metadat",pid=3697,fd=8)) ESTAB 0 0 172.17.1.10:45304 172.17.1.10:5672 users:(("neutron-metadat",pid=3697,fd=9)) Since RHOSP 13 Z11 you will get the following output: [root@pluto-controller0-0 ~]# docker exec -it neutron_metadata_agent bash ()[neutron@pluto-controller0-0 /]$ ss -ntp | grep 33028 ESTAB 0 0 192.168.1.1:33028 192.168.1.1:5672 users:(("/usr/bin/python",pid=330542,fd=9)) ESTAB 0 0 192.168.1.1:5672 192.168.1.1:33028 I obtained details for connection above by looking through rabbit logs: =INFO REPORT==== 20-Mar-2020::16:26:56 === accepting AMQP connection <0.32367.46> (192.168.1.1:33028 -> 192.168.1.1:5672) =INFO REPORT==== 20-Mar-2020::16:26:56 === Connection <0.32367.46> (192.168.1.1:33028 -> 192.168.1.1:5672) has a client-provided name: neutron-metadata-agent:330542:cae0cd31-33ca-4462-9f14-5d295d7e282a =INFO REPORT==== 20-Mar-2020::16:26:56 === connection <0.32367.46> (192.168.1.1:33028 -> 192.168.1.1:5672 - neutron-metadata-agent:330542:cae0cd31-33ca-4462-9f14-5d295d7e282a): user 'guest' authenticated and granted access to vhost '/' [1] https://github.com/openstack/tripleo-common/blob/stable/queens/healthcheck/neutron-l3 [2] https://github.com/openstack/tripleo-common/blob/stable/queens/healthcheck/common.sh#L14 Version-Release number of selected component (if applicable): - iproute-4.11.0-25.el7_7.2.x86_64 Tue Mar 3 15:48:02 2020 - kernel-3.10.0-1062.12.1.el7.x86_64 Tue Mar 3 15:50:14 2020 kernel-tools-3.10.0-1062.12.1.el7.x86_64 Tue Mar 3 15:50:31 2020 kernel-tools-libs-3.10.0-1062.12.1.el7.x86_64 Tue Mar 3 15:48:28 2020 - docker-1.13.1-109.gitcccb291.el7_7.x86_64 Tue Mar 3 16:35:23 2020 docker-client-1.13.1-109.gitcccb291.el7_7.x86_64 Tue Mar 3 16:33:16 2020 docker-common-1.13.1-109.gitcccb291.el7_7.x86_64 Tue Mar 3 16:33:15 2020 docker-rhel-push-plugin-1.13.1-109.gitcccb291.el7_7.x86_64 Tue Mar 3 16:31:58 2020 - 192.168.10.1:8787/rhosp13/openstack-neutron-metadata-agent 13.0-115 04933a9d64bd 2 weeks ago 791 MB 192.168.10.1:8787/rhosp13/openstack-neutron-openvswitch-agent 13.0-114 ac4271f58cfc 2 weeks ago 822 MB 192.168.10.1:8787/rhosp13/openstack-neutron-dhcp-agent 13.0-114 16534fef2ce7 2 weeks ago 943 MB How reproducible: Customer simply deployed latest RHOSP 13 and faced this issue
*** This bug has been marked as a duplicate of bug 1813758 ***