Prechecks fail for certain interfaces

Bug #1645954 reported by Christian Tardif
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned

Bug Description

The interface defined in globals.xml is called br-mgmt, which is defined, on the hosts, as:

enp1s0f1 -\
            ---> bond0 ---> bond0.210 ---> br-mgmt
enp3s0 -/

br-mgmt being a bridged interface from bond0.210 vlan interface for bond0, which is in turn a bonding interface for eth0 and eth1, if I'm expressing myself correctly.

br-mgmt has an IP interface that is reachable from the lan, so properly configured. If, for testing purposes, I set network_interface to bond0 (which also has an IP address), prechecks work correctly. But when I set br-mgmt as designed, prechecks fails at the first check:

TASK [prechecks : Checking free port for Aodh API] *****************************
fatal: [openstack1]: FAILED! => {"failed": true, "msg": "ERROR! 'dict object' has no attribute u'ansible_br-mgmt'"}

Interfaces are defined as:

# interface br-mgmt configuration
auto br-mgmt
iface br-mgmt inet static
  address 192.168.210.25
  netmask 255.255.255.0
  bridge_ports bond0.210
  bridge_stp off

# interface bond0 configuration
auto bond0
iface bond0 inet static
  address 192.168.101.25
  netmask 24
  gateway 192.168.101.3
  hwaddress 76:ff:c8:e2:3e:4c
  bond-lacp-rate 1
  bond-miimon 100
  bond-mode 802.3ad
  bond-slaves none

# interface bond0.210 configuration
auto bond0.210
iface bond0.210 inet manual

# interface enp1s0f1 configuration
auto enp1s0f1
iface enp1s0f1 inet manual
  bond-master bond0
  bond-mode 802.3ad

# interface enp3s0 configuration
auto enp3s0
iface enp3s0 inet manual
  bond-master bond0
  bond-mode 802.3ad

Any idea why prechecks would fail in such an environment ?

Revision history for this message
Christian Tardif (christian-tardif) wrote :

FOund out the issue, though I'd like to understant why. That's the "-" in the middle of the interface name that breaks prechecks. If I remove it, or change it to "_", then prechecks work, strangely enough...

Changed in kolla:
importance: Undecided → Medium
status: New → Triaged
Changed in kolla:
milestone: none → ocata-3
Changed in kolla:
milestone: ocata-3 → ocata-rc1
Changed in kolla:
milestone: ocata-rc1 → pike-1
Changed in kolla:
milestone: pike-2 → pike-3
Changed in kolla:
milestone: pike-3 → pike-rc1
Changed in kolla:
milestone: pike-rc1 → queens-1
Changed in kolla:
milestone: queens-2 → queens-3
Changed in kolla:
milestone: queens-3 → queens-rc1
Changed in kolla:
milestone: queens-rc1 → queens-rc2
Changed in kolla:
milestone: queens-rc2 → rocky-1
Changed in kolla:
milestone: rocky-2 → rocky-3
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
importance: Medium → Undecided
status: Triaged → 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.