Bug 1315725 - Packstack fails to configure Compute Node doing ML2&OVS&VLAN deployment
Summary: Packstack fails to configure Compute Node doing ML2&OVS&VLAN deployment
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: Liberty
Hardware: x86_64
OS: Linux
Target Milestone: ---
: Kilo
Assignee: Martin Magr
QA Contact: Shai Revivo
Depends On:
TreeView+ depends on / blocked
Reported: 2016-03-08 13:28 UTC by Boris Derzhavets
Modified: 2016-05-18 10:49 UTC (History)
4 users (show)

Fixed In Version: openstack-packstack-7.0.1-0.20160427184017.be2733f.el7.centos.noarch
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-05-18 10:49:41 UTC

Attachments (Terms of Use)
Answer filed been used for 3 Node deployment Controller/Network,Compute,Storage nodes (10.49 KB, text/plain)
2016-03-08 13:28 UTC, Boris Derzhavets
no flags Details

System ID Private Priority Status Summary Last Updated
OpenStack gerrit 305649 0 None None None 2016-05-18 10:49:41 UTC

Description Boris Derzhavets 2016-03-08 13:28:59 UTC
Created attachment 1134169 [details]
Answer filed been used for 3 Node deployment Controller/Network,Compute,Storage nodes

Description of problem:

Ethernet interface eth1 supposed to support vm/data VLAN tagged network connection to Controller/Network Node doesn't become a port of OVS bridge br-eth1. Br-eth1 OVS bridge is not configured on Compute node. File openvswitch_agent.ini is missing required lines, ml2_conf.ini is absent at all. So, neutron-openvswitch-agent at start up is unable to configure required bridges and ports on Compute Node.

Compute Node :-
1.Block is absent on Compute
Bridge "br-eth1"
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
        Port "eth1"
            Interface "eth1"
        Port "phy-br-eth1"
            Interface "phy-br-eth1"
                type: patch
                options: {peer="int-br-eth1"}

2.Block is absent on Compute
Port "int-br-eth1"
            Interface "int-br-eth1"
                type: patch
                options: {peer="phy-br-eth1"}
OVS/VLAN configuration on Compute node should be done manually via updating
required files in /etc/neutron/plugins/ml2 folder and copying over from Controller ifcfg-br-eth1 and ifcfg-eth1 into /etc/sysconfig/network-scripts

Afterwards :-

# openstack-service restart
# chkconfig network on
# systemctl stop Network Manager
# systemctl disable Network Manager 
# service network restart

brought Compute Node's OVS configuration to expected status.

Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:

1.Update attached file for Controller/Network && Compute two node deployment
  Set :-
2.packstack answer-file=./answerVLAN.txt

3.SSH to Compute node and run `ovs-vsctl show` right after packstack
  completion to make sure that nothing was done by packstack run.

Actual results:

Manual OVS configuration is required on Compute Node(s)

Expected results:

Packstack did OVS configuration properly on Compute Node(s)
As,actually, happens via same answer-file on RDO Kilo.

Additional info:

Comment 1 Boris Derzhavets 2016-03-08 13:32:59 UTC
Target release Liberty. It works on Kilo.

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