RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1095401 - Packstack failed to configure ML2 to work with OVS and VLAN
Summary: Packstack failed to configure ML2 to work with OVS and VLAN
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: Icehouse
Assignee: Lukas Bezdicka
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-07 15:32 UTC by Moti Asayag
Modified: 2015-03-27 20:24 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-27 20:24:13 UTC
Embargoed:


Attachments (Terms of Use)
packstack-answers.txt (17.55 KB, text/plain)
2014-05-07 15:32 UTC, Moti Asayag
no flags Details

Description Moti Asayag 2014-05-07 15:32:52 UTC
Created attachment 893337 [details]
packstack-answers.txt

Description of problem:
Packstack failed to install neutron when configured with ml2 as the layer-2 plugin, openvswitch as the ml2 driver and vlan as the tenant network type.

Version-Release number of selected component (if applicable):
rdo-release-icehouse-3

How reproducible:
always.

Steps to Reproduce:
1. Invoke packstack with the attached answer file.

Actual results:
Installation fails with the error as pasted below.

Expected results:
Installation should succeed.

Additional info:
-------------- pack stack output -----------------
Applying 127.0.0.1_neutron.pp
127.0.0.1_neutron.pp:                             [ ERROR ]    
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 127.0.0.1_neutron.pp
Error: Duplicate declaration: Package[neutron-plugin-ovs] is already declared in file /var/tmp/packstack/da954d6a6b2846918eff90174c851ad4/manifests/127.0.0.1_neutron.pp:69; cannot redeclare at /var/tmp/packstack/da954d6a6b2846918eff90174c851ad4/modules/neutron/manifests/plugins/ml2.pp:164 on node localhost.tlv.redhat.com
You will find full trace in log /var/tmp/packstack/20140507-063517-bgDhtD/manifests/127.0.0.1_neutron.pp.log
Please check log file /var/tmp/packstack/20140507-063517-bgDhtD/openstack-setup.log for more information

-------------- openstack-setup.log ---------------

2014-05-07 06:40:15::ERROR::run_setup::892::root:: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 887, in main
    _main(confFile)
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 574, in _main
    runSequences()
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 553, in runSequences
    controller.runAllSequences()
  File "/usr/lib/python2.6/site-packages/packstack/installer/setup_controller.py", line 84, in runAllSequences
    sequence.run(self.CONF)
  File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 96, in run
    step.run(config=config)
  File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 43, in run
    raise SequenceError(str(ex))
SequenceError: Error appeared during Puppet run: 127.0.0.1_neutron.pp
Error: Duplicate declaration: Package[neutron-plugin-ovs] is already declared in file /var/tmp/packstack/da954d6a6b2846918eff90174c851ad4/manifests/127.0.0.1_neutron.pp:69; cannot redeclare at /var/tmp/packstack/da954d6a6b2846918eff90174c851ad4/modules/neutron/manifests/plugins/ml2.pp:164 on node localhost.tlv.redhat.comESC[0m
You will find full trace in log /var/tmp/packstack/20140507-063517-bgDhtD/manifests/127.0.0.1_neutron.pp.log

Comment 2 Lars Kellogg-Stedman 2015-03-27 20:24:13 UTC
This behavior appears to have been resolved in the latest (RDO Juno) packages.  With openstack-packstack-2014.2-0.18.dev1462.gbb05296.fc22.noarch and the following configuration...

CONFIG_NEUTRON_ML2_TYPE_DRIVERS=vxlan,vlan,flat
CONFIG_NEUTRON_ML2_TENANT_NETWORK_TYPES=vlan
CONFIG_NEUTRON_ML2_VLAN_RANGES=physnet-eth1:100:200

...I am able to run packstack through to completion without any errors.


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