container_restart play looking for containers on the object hosts

Bug #1417164 reported by Jacob Wagner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Critical
Kevin Carter
Juno
Fix Released
Critical
Kevin Carter
Trunk
Fix Released
Critical
Kevin Carter

Bug Description

Currently when running the container_restart play, it is looking for container running on all hosts. When it looks for containers on the swift object hosts it marks them as a failure due to no containers existing on the hosts (when i say looking it is using the inventory json and there is nothing inside the array so it fails)

16:15:01 PLAY [hosts] ******************************************************************
16:15:01
16:15:01 TASK: [container_restart | Test Container Networking] *************************
16:15:01 fatal: [node107] => host not found:
16:15:01 fatal: [node120] => host not found:
16:15:01 fatal: [node119] => host not found:
16:15:01 ok: [node92] => (item=node92_rsyslog_container-3dc57e35) => {"changed": false, "elapsed": 0, "item": "node92_rsyslog_container-3dc57e35", "path": null, "port": 22, "search_regex": "OpenSSH", "state": "started"}

This is causing the setup-host play to fail

Revision history for this message
Jacob Wagner (swagner1104) wrote :
Download full text (12.9 KiB)

jenkins@node89:~/os-ansible-deployment$ scripts/inventory-manage.py -f /var/lib/jenkins/rpc_deploy/rpc_inventory.json -l -s physical_host
+------------------------------------------------+----------+---------------------+---------------+----------------+------------------+--------------------+
| container_name | is_metal | component | physical_host | tunnel_address | ansible_ssh_host | container_types |
+------------------------------------------------+----------+---------------------+---------------+----------------+------------------+--------------------+
| node107 | True | swift_cont | node107 | None | 10.127.101.90 | node107_containers |
| node116 | True | None | node116 | None | 10.127.101.110 | node116_containers |
| node116_cinder_api_container-d5656137 | False | cinder_api | node116 | None | 172.29.236.51 | None |
| node116_galera_container-5817007a | False | galera | node116 | None | 172.29.236.55 | None |
| node116_glance_container-2d84441f | False | glance_api | node116 | None | 172.29.239.166 | None |
| node116_heat_apis_container-48af9e64 | False | heat_api_cloudwatch | node116 | None | 172.29.237.224 | None |
| node116_heat_engine_container-dfd5bb8d | False | heat_engine | node116 | None | 172.29.238.78 | None |
| node116_horizon_container-d8b2d478 | False | horizon | node116 | None | 172.29.238.69 | None |
| node116_keystone_container-8f568555 | False | keystone | node116 | None | 172.29.236.174 | None |
| node116_memcached_container-1a9124c6 | False | memcached | node116 | None | 172.29.237.157 | None |
| node116_neutron_agents_container-d77bffec | False | neutron_agent | node116 | 172.29.243.198 | 172.29.238.32 | None |
| node116_neutron_server_container-7f33b305 | False | neutron_server | node116 | None | 172.29.236.41 | None |
| node116_nova_api_ec2_container-bdcd3c46 | False | nova_api_ec2 | node116 | None | 172.29.237.31 | None |
| node116_nova_api_metadata_container-9e64f185 | False | nova_api_metadata | node116 | None | 172.29.239.1 | None |
| node116_nova_api_os_compute_container-9834cd0e | False | nova_api_os_compute | node116 | None | 172.29.236.199 | None |
| node116_nova_cert_container-62cf7f35 | False | nova_cert | node116 | None | 172.29.237.211 | None |
| node116_nova_conductor_container-3c8b0445 | False | nova_conductor ...

Changed in openstack-ansible:
status: New → Triaged
Revision history for this message
Kevin Carter (kevin-carter) wrote :

This is resolved in master and needs to be cherry-picked to Juno.

The Cherry-pick has been done here: https://review.openstack.org/#/c/152203/

Revision history for this message
Kevin Carter (kevin-carter) wrote :

@Jacob Wagner - This should be resolved in the Juno branch please retest as soon as possible.

Revision history for this message
Jacob Wagner (swagner1104) wrote :

@Kevin Carter - This has been resolved on the Juno branch. Thanks for the merge!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.