fatal error in os-octavia-install.yml in xena

Bug #1980226 reported by Peter Struys
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Expired
Undecided
Unassigned

Bug Description

Running Stable/Xena for some time with success, then adding octavia project

When following https://docs.openstack.org/openstack-ansible-os_octavia/latest/configure-octavia.html and I use parameter "octavia_provider_inventory_net_name: lbaas" in user_variables.yml the playbook os-octavia-install fails with 'dict object' has no attribute 'ip_from_q'.

When following docs from previous version victoria (see https://docs.openstack.org/openstack-ansible-os_octavia/victoria/configure-octavia.html) and I use the parameter octavia_container_network_name: lbaas_address the playbook ends with success.

The complete error is :

fatal: [jommeke_octavia_server_container-36316abb]: FAILED! => {"msg": "{% for host in groups[octavia_hm_group] %}{{ hostvars[host]['container_networks'][octavia_container_network_name]
['address'] }}{% if not loop.last %},{% endif %}{% endfor %}: {{ octavia_provider_network['ip_from_q'] }}_address: 'dict object' has no attribute 'ip_from_q'"}

Don't understand fully why.

regards
Peter

Revision history for this message
Dmitriy Rabotyagov (noonedeadpunk) wrote :

Hi Peter.

I believe you end up with that error as there's some mis-configuration in openstack_user_config.yml
As you rightfully mentioned, according to https://docs.openstack.org/openstack-ansible-os_octavia/victoria/configure-octavia.html#vlan-networking-scenario you need to describe networks that are mapped to the container. In the example, one of the keys is `ip_from_q: "lbaas"`. Also, you should define lbaas network netmask in cidr_networks.

It would be helpful to debug if you also provided your configuration, as without it it's hard to understand what exactly went wrong with Octavia setup.

Changed in openstack-ansible:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openstack-ansible because there has been no activity for 60 days.]

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