Created attachment 1139660 [details] Answer filed been used for 2 Node deployment Controller/Network,Compute Description of problem: Answer file is attached ( version which worked for Kilo) Version-Release number of selected component (if applicable): [root@ServerCentOS01 ~(keystone_boris)]# rpm -qa \*openstack-packstack\* openstack-packstack-puppet-8.0.0-0.20160316101826.9fd26e8.el7.centos.noarch openstack-packstack-8.0.0-0.20160316101826.9fd26e8.el7.centos.noarch [root@ServerCentOS01 ~(keystone_boris)]# rpm -qa \*nova-common\* openstack-nova-common-13.0.0.0-0.20160322123219.ce6dbea.el7.centos.noarch How reproducible: 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 folder. Afterwards :- # openstack-service restart # chkconfig network on # systemctl stop Network Manager # systemctl disable Network Manager # service network restart Steps to Reproduce: 1. # yum -y install yum-plugin-priorities # cd /etc/yum.repos.d # curl -O https://trunk.rdoproject.org/centos7-mitaka/delorean-deps.repo # curl -O https://trunk.rdoproject.org/centos7-mitaka/current-passed-ci/delorean.repo on both nodes 2. packstack --answer-file=./answerVLAN2NODE.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:
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.