Bug 1282416 - Configuring provisioning network on bond fails via tripleO templates
Summary: Configuring provisioning network on bond fails via tripleO templates
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 7.0 (Kilo)
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: 10.0 (Newton)
Assignee: Jiri Stransky
QA Contact: Shai Revivo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-16 10:50 UTC by Jaison Raju
Modified: 2019-09-12 09:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 15:33:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
network yaml files (3.92 KB, application/zip)
2015-11-16 11:09 UTC, Jaison Raju
no flags Details

Description Jaison Raju 2015-11-16 10:50:54 UTC
Description of problem:
Configuring provisioning network on bond fails via tripleO templates .

              members:
                -
                  type: ovs_bond
                  name: bond-prov
                  ovs_options: {get_param: BondInterfaceOvsOptions}
                  members:
                    -
                      type: interface
                      name: em1
                      primary: true
                    -
                      type: interface
                      name: em2

The node gets written with image but the network configuration seen after reboot
makes it inaccessible .

em1 seems to have dhcp IP address , but em2 seems to have discovery IP address .
The stack create seems to be stuck indefinitely .

Version-Release number of selected component (if applicable):
RHOS7
OSPD7
openstack-tripleo-heat-templates-0.8.6-71.el7ost.noarch
openstack-tripleo-0.0.7-0.1.1664e566.el7ost.noarch
Due to discovery IP on em2 , cannot ssh from director to em1 / dhcp IP .

How reproducible:
Not confirmed .

Steps to Reproduce:
1. Configure controllers with 2 nics as bond .
2.
3.

Actual results:
em1 & em2 are not bonded & em2 has discovery IP & em1 has dhcp IP .

Expected results:
Bond is created using em1 & em2 & has an accessible IP over dhcp range .

Additional info:
to access node at this point, we copy ssh private key to compute & ssh from compute .
Disabling em2 also allow access to controller at this point .

Comment 2 Jaison Raju 2015-11-16 11:09:01 UTC
Created attachment 1094849 [details]
network yaml files

Comment 6 Mike Burns 2016-04-07 20:57:01 UTC
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 8 Dan Sneddon 2016-10-14 15:33:42 UTC
Bonds on the provisioning network should work, certainly with OSP-Director 7.3+. We do test bonding via the provisioning network.

The behavior where some of the bond slaves may receive a discovery IP is transient, and that IP should disappear when the bond is configured.


Note You need to log in before you can comment on or make changes to this bug.