Comment 6 for bug 2002645

Oh, but that's a bug!

So I have dummy playbook:

```
  - hosts: az1-controller_hosts,dev2-az1-os-control01_cinder_api_container-7a5de4f0
    tasks:
    - debug:
        msg: "{{ item }}"
      with_items:
        - "{{ management_address }}"
        - "{{ hostvars[inventory_hostname]['ansible_host'] }}"
```

In openstack_user_config:

```
cidr_networks:
  container: 10.21.8.0/22
.....
az1-controller_hosts: &controller_az1
  dev2-az1-os-control01:
    ip: 10.21.0.21
```

And it's output is:

```
  ok: [dev2-az1-os-control01] => (item=10.21.0.21) => {
      "msg": "10.21.0.21"
  }
  ok: [dev2-az1-os-control01] => (item=10.21.0.21) => {
      "msg": "10.21.0.21"
  }
  ok: [dev2-az1-os-control01_cinder_api_container-7a5de4f0] => (item=10.21.9.245) => {
      "msg": "10.21.9.245"
  }
  ok: [dev2-az1-os-control01_cinder_api_container-7a5de4f0] => (item=10.21.9.245) => {
      "msg": "10.21.9.245"
  }
```

At the time I have /22 networks there. This also means, that services that may run on bare metal will listen not on mgmt IP, but on SSH one.
So it's independent bug that needs fixing IMO.