openstack-ansible

physical_skel containers group has unexpected hosts

Bug #1672604 reported by Jimmy McCrory
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-ansible
Confirmed
Low
Jimmy McCrory

Bug Description

For each of the service environment files, the containers group within the phsyical_skel that belongs_to 'all_containers' contains either all containers within an environment orno hosts at all.

For example:

https://github.com/openstack/openstack-ansible/blob/master/playbooks/inventory/env.d/nova.yml#L103-L105
nova.yml
--------
physical_skel:
  compute-infra_containers:
    belongs_to:
      - all_containers

In openstack_inventory.json:

    "compute-infra_containers": {
        "children": [
            "aio1-host_containers"
        ],
        "hosts": []
    }

# ansible compute-infra_containers --list-hosts
Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml "
  hosts (23):
    aio1_nova_scheduler_container-85a375e2
    aio1_horizon_container-5eb540a5
    aio1_utility_container-9c101589
    aio1_keystone_container-e4027a51
    aio1_cinder_scheduler_container-c86a55ca
    aio1_swift_proxy_container-5248201b
    aio1_neutron_server_container-dcb85897
    aio1_repo_container-ad388db2
    aio1_glance_container-ef5938dd
    aio1_neutron_agents_container-bf2d9db1
    aio1_nova_api_os_compute_container-b89c2971
    aio1_designate_container-e0cd8d08
    aio1_nova_api_metadata_container-cc5225c1
    aio1_nova_console_container-a12ec46b
    aio1_nova_conductor_container-3e001513
    aio1_cinder_api_container-d2d1c715
    aio1_galera_container-0997b13b
    aio1_rsyslog_container-fb962777
    aio1_rabbit_mq_container-74ed1a51
    aio1_nova_api_placement_container-cfe66098
    aio1_memcached_container-defdb9b1
    aio1_heat_apis_container-b3567cef
    aio1_heat_engine_container-28cf25be

https://github.com/openstack/openstack-ansible/blob/master/playbooks/inventory/env.d/memcache.yml#L33-L36
memcache.yml
-----------
physical_skel:
  memcaching_containers:
    belongs_to:
      - all_containers

In openstack_inventory.json:

    "memcaching_containers": {
        "children": [],
        "hosts": []
    }

# ansible memcaching_containers --list-hosts
Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml "
 [WARNING]: No hosts matched, nothing to do

  hosts (0):

Revision history for this message
Jean-Philippe Evrard (jean-philippe-evrard) wrote :

On master.

Andy McCrae (andrew-mccrae)
Changed in openstack-ansible:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Andy McCrae (andrew-mccrae) wrote :

Confirmed - from an AIO inventory right now:

    "compute-infra_containers": {
        "children": [
            "aio1-host_containers"
        ],
        "hosts": []
    },
...
    "memcaching_containers": {
        "children": [],
        "hosts": []
    },
...

I think the reason behind this may be related to: in the user_config.yml (or conf.d/x.yml files) you will have:
"compute-infra_hosts".

Whereas - in the AIO you do not have "memcaching_hosts"

==========

What is the desired outcome though? I agree the inventory generation around env.d/x.yml files is horrible but I'm not sure how it should look in regards to this bug.

Revision history for this message
Jimmy McCrory (jimmy-mccrory) wrote :

I was expecting the children of compute-infra_containers to be all the groups under the container_skel that say belongs_to compute-infra_containers.

https://github.com/openstack/openstack-ansible/blob/master/playbooks/inventory/env.d/nova.yml#L40

The same for memcaching_containers.
https://github.com/openstack/openstack-ansible/blob/master/playbooks/inventory/env.d/memcache.yml#L23-L25

These files just don't seem very intuitive or accurate.

Revision history for this message
Jimmy McCrory (jimmy-mccrory) wrote :

Looks like it's been like this since at least Juno

# ansible compute_containers --list-hosts
    aio1_nova_scheduler_container-63806a29
    aio1_nova_conductor_container-fe964086
    aio1_cinder_api_container-6a29b8e1
    aio1_elasticsearch_container-bdcf3cde
    aio1_horizon_container-1aca4fd5
    aio1_utility_container-4fd4a1a0
    aio1_keystone_container-9caa0955
    aio1_nova_cert_container-305af23f
    aio1_galera_container-0dc33941
    aio1_nova_api_ec2_container-1f56ed87
    aio1_nova_spice_console_container-25bf02dc
    aio1_swift_proxy_container-dba7ea0e
    aio1_neutron_server_container-16c41fe7
    aio1_rabbit_mq_container-c506e48b
    aio1_cinder_volumes_container-8b6a1cff
    aio1_glance_container-9f82b948
    aio1_neutron_agents_container-3a436b06
    aio1_nova_api_os_compute_container-8a6d93df
    aio1_rsyslog_container-622209ca
    aio1_heat_engine_container-e3457a53
    aio1_nova_api_metadata_container-b93832e3
    aio1_kibana_container-66951e9c
    aio1_logstash_container-19c41a51
    aio1_heat_apis_container-364508a1
    aio1_memcached_container-2fe0585b

    "compute_containers": {
        "children": [
            "aio1_containers"
        ],
        "hosts": []
    }

Jimmy McCrory (jimmy-mccrory)
Changed in openstack-ansible:
assignee: nobody → Jimmy McCrory (jimmy-mccrory)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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