new openstack installation fails

Bug #1709497 reported by admin0
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Invalid
Undecided
Unassigned

Bug Description

new setup, greenfield.
all servers are ubuntu 16.04 LTS with the recommended packages installed.

## Issue
/opt/openstack-ansible/playbooks(stable/ocata) # openstack-ansible setup-hosts.yml

Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml "

PLAY [Install unbound DNS resolver client configurations] ************************************************************************************************

TASK [Gathering Facts] ***********************************************************************************************************************************
Tuesday 08 August 2017 22:59:33 +0000 (0:00:00.110) 0:00:00.110 ********

TASK [Set unbound physical hosts fact] *******************************************************************************************************************
Tuesday 08 August 2017 22:59:33 +0000 (0:00:00.054) 0:00:00.165 ********

TASK [Apply resolver sorting] ****************************************************************************************************************************
Tuesday 08 August 2017 22:59:34 +0000 (0:00:00.043) 0:00:00.208 ********

TASK [Set resolver IP list fact] *************************************************************************************************************************
Tuesday 08 August 2017 22:59:34 +0000 (0:00:00.036) 0:00:00.245 ********

TASK [Set resolver rotate when physical_host is not an unbound host] *************************************************************************************
Tuesday 08 August 2017 22:59:34 +0000 (0:00:00.033) 0:00:00.279 ********

TASK [resolvconf : Gather variables for each operating system] *******************************************************************************************
Tuesday 08 August 2017 22:59:34 +0000 (0:00:00.030) 0:00:00.309 ********
fatal: [v11]: FAILED! => {"failed": true, "msg": "No file was found when using with_first_found. Use the 'skip: true' option to allow this task to be skipped if no files are found"}
fatal: [v12]: FAILED! => {"failed": true, "msg": "No file was found when using with_first_found. Use the 'skip: true' option to allow this task to be skipped if no files are found"}
fatal: [v13]: FAILED! => {"failed": true, "msg": "No file was found when using with_first_found. Use the 'skip: true' option to allow this task to be skipped if no files are found"}
fatal: [c7]: FAILED! => {"failed": true, "msg": "No file was found when using with_first_found. Use the 'skip: true' option to allow this task to be skipped if no files are found"}
fatal: [c8]: FAILED! => {"failed": true, "msg": "No file was found when using with_first_found. Use the 'skip: true' option to allow this task to be skipped if no files are found"}
fatal: [v14]: FAILED! => {"failed": true, "msg": "No file was found when using with_first_found. Use the 'skip: true' option to allow this task to be skipped if no files are found"}

PLAY RECAP ***********************************************************************************************************************************************
c7 : ok=0 changed=0 unreachable=0 failed=1
c8 : ok=0 changed=0 unreachable=0 failed=1
v11 : ok=0 changed=0 unreachable=0 failed=1
v12 : ok=0 changed=0 unreachable=0 failed=1
v13 : ok=0 changed=0 unreachable=0 failed=1
v14 : ok=0 changed=0 unreachable=0 failed=1

Tuesday 08 August 2017 22:59:34 +0000 (0:00:00.059) 0:00:00.368 ********
===============================================================================
resolvconf : Gather variables for each operating system ----------------- 0.06s
Gathering Facts --------------------------------------------------------- 0.05s
Set unbound physical hosts fact ----------------------------------------- 0.04s
Apply resolver sorting -------------------------------------------------- 0.04s
Set resolver IP list fact ----------------------------------------------- 0.03s
Set resolver rotate when physical_host is not an unbound host ----------- 0.03s
------------------------------------------------------------
/opt/openstack-ansible/playbooks(stable/ocata) #

The setup will ONLY continue if unbound_hosts are set

But after that, it runs and fails at the step: ... installing distro packages

This is because the /etc/resolv.conf points to the *not yet created* IP addresses.

So the whole process is totally stuck.

admin0 (shashi-eu)
description: updated
Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

Could you paste your user config? The play should be skipped if no hosts match (no hosts are in the scope of the play).

Revision history for this message
admin0 (shashi-eu) wrote :
Download full text (6.2 KiB)

---
cidr_networks:
  container: 172.29.236.0/22
  tunnel: 172.29.240.0/22
  storage: 172.29.244.0/22

used_ips:
  - "172.29.236.1,172.29.236.99"
  - "172.29.240.1,172.29.240.99"
  - "172.29.244.1,172.29.244.99"
  - "172.29.248.1,172.29.248.99"

global_overrides:
  #
  # The below domain name must resolve to an IP address
  # in the CIDR specified in haproxy_keepalived_external_vip_cidr.
  # If using different protocols (https/http) for the public/internal
  # endpoints the two addresses must be different.
  #
  internal_lb_vip_address: my-int.domain.cloud
  external_lb_vip_address: my.domain.cloud
  tunnel_bridge: "br-vxlan"
  management_bridge: "br-mgmt"
  provider_networks:
    - network:
        container_bridge: "br-mgmt"
        container_type: "veth"
        container_interface: "eth1"
        ip_from_q: "container"
        type: "raw"
        group_binds:
          - all_containers
          - hosts
        is_container_address: true
        is_ssh_address: true
    - network:
        container_bridge: "br-vxlan"
        container_type: "veth"
        container_interface: "eth10"
        ip_from_q: "tunnel"
        type: "vxlan"
        range: "100000:999999"
        net_name: "vxlan"
        group_binds:
          - neutron_linuxbridge_agent
    - network:
        container_bridge: "br-net"
        container_type: "veth"
        container_interface: "eth12"
        host_bind_override: "eth12"
        type: "flat"
        net_name: "flat"
        group_binds:
          - neutron_linuxbridge_agent
    - network:
        container_bridge: "br-pub"
        container_type: "veth"
        container_interface: "eth13"
        host_bind_override: "eth13"
        type: "flat"
        net_name: "flat"
        group_binds:
          - neutron_linuxbridge_agent
    - network:
        container_bridge: "br-vlan"
        container_type: "veth"
        container_interface: "eth11"
        type: "vlan"
        range: "1:4090"
        net_name: "vlan"
        group_binds:
          - neutron_linuxbridge_agent
    - network:
        container_bridge: "br-storage"
        container_type: "veth"
        container_interface: "eth2"
        ip_from_q: "storage"
        type: "raw"
        group_binds:
          - glance_api
          - cinder_api
          - cinder_volume
          - nova_compute

sahara-infra_hosts:
  v11:
    ip: 172.29.236.11
  v12:
    ip: 172.29.236.12
  v13:
    ip: 172.29.236.13

trove-infra_hosts:
  v11:
    ip: 172.29.236.11
  v12:
    ip: 172.29.236.12
  v13:
    ip: 172.29.236.13

magnum-infra_hosts:
  v11:
    ip: 172.29.236.11
  v12:
    ip: 172.29.236.12
  v13:
    ip: 172.29.236.13

shared-infra_hosts:
  v11:
    ip: 172.29.236.11
  v12:
    ip: 172.29.236.12
  v13:
    ip: 172.29.236.13

repo-infra_hosts:
  v11:
    ip: 172.29.236.11
  v12:
    ip: 172.29.236.12
  v13:
    ip: 172.29.236.13

haproxy_hosts:
  v11:
    ip: 172.29.236.11
  v12:
    ip: 172.29.236.12
  v13:
    ip: 172.29.236.13

log_hosts:
  v14:
    ip: 172.29.236.14

identity_hosts:
  v11:
    ip: 172.29.236.11
  v12:
    ip: 172.29.236.12
  v13:
    ip: 172.29.236.13

storage-infra_hosts:
  v11:
    ip: 172.29.236.11
  v12:
    ip: 172.29.236.12
 ...

Read more...

Revision history for this message
admin0 (shashi-eu) wrote :

culprit found.

instead of the usual way

git clone repo ; git checkout stable/ocata

this time, it was accidently

git clone repo ; git checkout -b stable/ocata

Changed in openstack-ansible:
status: New → Invalid
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.