I have a compute host that looks like this:
"_meta": {
"hostvars": {
"lsn-d3277": {
"ansible_ssh_host": "10.10.9.103",
"component": "nova_compute",
"container_address": "10.10.9.103",
"container_name": "lsn-d3277",
"container_networks": {},
"container_types": "lsn-d3277_containers",
"is_metal": true,
"physical_host": "lsn-d3277",
"physical_host_group": "compute_hosts",
"properties": {
"container_release": "trusty",
"is_metal": true,
"service_name": "nova"
}
},
The host fails to deploy because:
TASK: [Set nova management bridge (is_metal)] *********************************
skipping: [lsn-d3277]
TASK: [Set nova management address (is_metal)] ********************************
fatal: [lsn-d3277] => One or more undefined variables: 'dict object' has no attribute u'br-mgmt'
It looks like the bug is here:
- name: Set nova management bridge (is_metal)
set_fact:
management_bridge: "{{ 'ansible_' + hostvars[inventory_hostname]['container_networks']['container_address']['bridge'] | replace('-', '_') }}"
when:
- hostvars[inventory_hostname]['container_networks']['container_address']['bridge'] is defined
- is_metal | bool
tags:
- nova-config
- name: Set nova management address (is_metal)
set_fact:
management_address: "{{ hostvars[inventory_hostname][management_bridge]['ipv4']['address'] }}"
when:
- is_metal | bool
tags:
- nova-config
- name: Set nova management bridge (is_metal no container network)
set_fact:
management_address: "{{ ansible_ssh_host }}"
when:
- hostvars[inventory_hostname]['container_networks']['container_address']['bridge'] is undefined
- is_metal | bool
tags:
- nova-config
Looking at the flow here I don't see how I could configure to reach "Set nova management bridge (is_metal no container network)", which is the appropriate task for my environment. There should be more filtering on "Set nova management address (is_metal)" .
When I add the below "when" to "Set nova management address (is_metal)" everything works as expected.
- hostvars[inventory_hostname]['container_networks']['container_address']['bridge'] is defined
This is maybe not the best filter to implement for the fix but it works great for me to bypass the failure and use the correct rule.
Looks like it is related to this recent change: http://