Install Contrail Task "Contrail default swift container and Temp-URL-Key creation" fails

[vicg3]

Trying to configure All in One with 2 interfaces (management and control/data network):

---mgmt network-------em1[Server]p6p1-----control/data network---- [Router] 10.8.128.x/25 .92 .92 10.92.100.x/24 .1

Here is instances.yaml file:

provider_config: bms: ssh_pwd: Juniper!1 ssh_user: root ssh_public_key: ssh_private_key: ntpserver: 10.8.4.105 nameserver: 10.8.4.105 domainsuffix: cse-wf.jnpr.net instances: bms1: provider: bms roles: openstack: config_database: config: control: analytics_database: analytics: webui: vrouter: PHYSICAL_INTERFACE: p6p1 VROUTER_GATEWAY: 10.92.100.1 openstack_compute: kubemanager: k8s_master: k8s_node: ip: 10.8.128.92

contrail_configuration: CONTAINER_REGISTRY: opencontrailnightly CONTRAIL_VERSION: ocata-master-58 UPGRADE_KERNEL: true RABBITMQ_NODE_PORT: 5673 AUTH_MODE: keystone KEYSTONE_AUTH_URL_VERSION: /v3 KEYSTONE_AUTH_ADMIN_PASSWORD: contrail123 CLOUD_ORCHESTRATOR: openstack VROUTER_GATEWAY: 10.92.100.1 PHYSICAL_INTERFACE: em1 CONTROL_DATA_NET_LIST: 10.92.100.0/24 AAA_MODE: cloud-admin KUBERNETES_CLUSTER_PROJECT: {}

kolla_config: customize: nova.conf: | [libvirt] virt_type=qemu cpu_mode=none kolla_globals: network_interface: "em1" kolla_internal_vip_address: "10.92.100.92" kolla_external_vip_address: "10.8.128.92" enable_haproxy: "no"_

Issue is that the "install_contrail" playbook is erroring out at the Task below.

TASK [Contrail default swift container and Temp-URL-Key creation] ************************************************************************* fatal: [10.8.128.92]: FAILED! => {"changed": true, "cmd": "docker exec kolla_toolbox bash -c 'source /var/lib/kolla/config_files/admin-openrc.sh; swift post -r '.r:*' contrail_container; swift post -m \"Temp-URL-Key:mykey\"'", "delta": "0:01:04.557185", "end": "2018-04-12 15:26:29.732715", "msg": "non-zero return code", "rc": 1, "start": "2018-04-12 15:25:25.175530", "stderr": "HTTPConnectionPool(host='10.8.128.92', port=8080): Max retries exceeded with url: /v1/AUTH_df269fdcb0dd469983dc5fd42dff04ad/contrail_container (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',))\nHTTPConnectionPool(host='10.8.128.92', port=8080): Max retries exceeded with url: /v1/AUTH_df269fdcb0dd469983dc5fd42dff04ad (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',))", "stderr_lines": ["HTTPConnectionPool(host='10.8.128.92', port=8080): Max retries exceeded with url: /v1/AUTH_df269fdcb0dd469983dc5fd42dff04ad/contrail_container (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',))", "HTTPConnectionPool(host='10.8.128.92', port=8080): Max retries exceeded with url: /v1/AUTH_df269fdcb0dd469983dc5fd42dff04ad (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 111] Connection refused',))"], "stdout": "", "stdout_lines": []} to retry, use: --limit @/root/contrail-ansible-deployer/playbooks/install_contrail.retry

PLAY RECAP ******************************************************************************************************************************** 10.8.128.92 : ok=373 changed=32 unreachable=0 failed=1 localhost : ok=9 changed=4 unreachable=0 failed=0

This is the last task in the /root/contrail-kolla-ansible/ansible/post-deploy-contrail.yaml file.

• name: Contrail default swift container and Temp-URL-Key creation shell: docker exec kolla_toolbox bash -c 'source /var/lib/kolla/config_files/admin-openrc.sh; swift post -r '.r:*' contrail_container; swift post -m "Temp-URL-Key:mykey"' when:
  • enable_swift_opencontrail | bool

[Andrey-mp]

@ramprackash @nitishkrishna Can you please check this issue?

[ramprackash]

When you have 2 interfaces that you want open stack running on, you need to use a virtual IP for each of the networks (10.8.128.X and 10.92.100.Y) and then enable_haproxy must be set to yes. (even though there is only one open stack node)

https://github.com/Juniper/contrail-ansible-deployer/wiki/Provisioning-F.A.Q#why-do-i-need-haproxy-and-virtual-ip-on-a-single-openstack-cluster