build 8: ubuntu-14.04 compute provision fails as contrail-lb container is restarting

Bug #1692169 reported by Sudheendra Rao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
New
Critical
Hari Prasad Killi
R4.0
New
Critical
Hari Prasad Killi

Bug Description

The compute provision fails as contrail-lb is restarting due to the below error on build8 ubuntu-14.04 on HA setups.

TASK [contrail/lb : Run script to get Tor Agent specific HAProxy configuration] ^M
^[[0;36mskipping: [localhost]^[[0m^M
^M
TASK [contrail/lb : Set the haproxy tor agent output] **************************^M
^[[0;31mfatal: [localhost]: FAILED! => {"failed": true, "msg": "The conditional check 'haproxy_toragent_stanza.stdout != ''' failed. The error was: error while evaluating conditional (haproxy_toragent_stanza.stdout != ''): 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/contrail-ansible-internal/playbooks/roles/contrail/lb/tasks/haproxy.yml': line 17, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Set the haproxy tor agent output\n ^ here\n"}^[[0m^M
        to retry, use: --limit @/contrail-ansible-internal/playbooks/contrail_lb.retry^M
^M
PLAY RECAP *********************************************************************^M
^[[0;31mlocalhost^[[0m : ^[[0;32mok=23 ^[[0m ^[[0;33mchanged=7 ^[[0m unreachable=0 ^[[0;31mfailed=1 ^[[0m^M

root@nodem10:/# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f5e39eef68bb 10.204.216.103:5100/ubuntu14mitaka8-contrail-lb:8 "/bin/sh -c /entry..." 6 hours ago Restarting (1) About a minute ago lb
root@nodem10:/#

root@nodem14:~# /opt/contrail/contrail_server_manager/provision_status.sh

+---------+---------------------+----------------+-------------------+
| id | status | ip_address | mac_address |
+---------+---------------------+----------------+-------------------+
| nodem14 | provision_completed | 10.204.216.103 | 0C:C4:7A:DC:42:C8 |
| nodem6 | provision_completed | 10.204.216.95 | 0C:C4:7A:DC:44:1E |
| nodem7 | provision_completed | 10.204.216.96 | 0C:C4:7A:DC:44:3A |
| nodem8 | provision_failed | 10.204.216.97 | 0C:C4:7A:DC:42:A2 |
| nodem9 | provision_failed | 10.204.216.98 | 0C:C4:7A:DC:44:22 |
| nodem10 | provision_completed | 10.204.216.99 | 0C:C4:7A:DC:44:3C |
+---------+---------------------+----------------+-------------------+

Setup is in failed state.

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.