kolla-ansible fails on dedicated tunnel_interface

Bug #1642521 reported by bjolo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
Undecided
Eduardo Gonzalez

Bug Description

when running kolla-ansible deploy/genconfig with a dedicated tunnel_interface, it fails on the controller nodes. The failure is correct in the sense that the tunnel_interface is missing. However, the controller nodes does not have a tunnel_interface configured since the controllers do not require to have a tunnel interface. (and should not have it) Tunnel interface is only needed on network and compute nodes

TASK [neutron : Copying over ml2_conf.ini dest={{ node_config_directory }}/{{ item }}/ml2_conf.ini, sources=[u'{{ role_path }}/templates/ml2_conf.ini.j2', u'{{ node_custom_config }}/neutron/ml2_conf.ini', u'{{ node_custom_config }}/neutron/{{ inventory_hostname }}/ml2_conf.ini'], vars={u'service_name': u'{{ item }}'}] ***
fatal: [eselde02u32.mydomain.net]: FAILED! => {"failed": true, "msg": "{{ hostvars[inventory_hostname]['ansible_' + tunnel_interface]['ipv4']['address'] }}: 'dict object' has no attribute u'ansible_bond0.820'"}
fatal: [eselde02u34.mydomain.net]: FAILED! => {"failed": true, "msg": "{{ hostvars[inventory_hostname]['ansible_' + tunnel_interface]['ipv4']['address'] }}: 'dict object' has no attribute u'ansible_bond0.820'"}
fatal: [eselde02u33.mydomain.net]: FAILED! => {"failed": true, "msg": "{{ hostvars[inventory_hostname]['ansible_' + tunnel_interface]['ipv4']['address'] }}: 'dict object' has no attribute u'ansible_bond0.820'"}

bjolo (bjorn-lofdahl)
summary: - kolla-ansible genconfig fails on tunnel_interface
+ kolla-ansible fails on dedicated tunnel_interface
description: updated
affects: kolla → kolla-ansible
Changed in kolla-ansible:
milestone: none → ocata-2
Changed in kolla-ansible:
milestone: ocata-2 → ocata-3
Changed in kolla-ansible:
milestone: ocata-3 → ocata-rc1
Changed in kolla-ansible:
milestone: ocata-rc1 → ocata-rc2
milestone: ocata-rc2 → pike-1
Changed in kolla-ansible:
milestone: pike-2 → pike-3
Changed in kolla-ansible:
status: New → In Progress
assignee: nobody → Eduardo Gonzalez (egonzalez90)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.openstack.org/463509
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=a3f957591c3cb6d44d8ed5629af644d5885be963
Submitter: Jenkins
Branch: master

commit a3f957591c3cb6d44d8ed5629af644d5885be963
Author: Eduardo Gonzalez <email address hidden>
Date: Tue May 9 10:55:54 2017 +0200

    Only use br-tun on network and compute nodes

    Neutron-server does not use br-tun at all,
    this is only needed at compute and network nodes.

    Change-Id: I0e11baa3fc8ee15c951cf4fc9aaa3a1d47819e81
    Closes-Bug: #1642521

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 5.0.0.0b3

This issue was fixed in the openstack/kolla-ansible 5.0.0.0b3 development milestone.

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.