Red Hat Bugzilla – Bug 1022058
Error: Local ip for ovs agent must be set when tunneling is enabled
Last modified: 2016-07-19 16:19:53 EDT
Created attachment 815028 [details]
Description of problem:
Fedora 19, multi-node install
2013-10-21 17:23:14::DEBUG::sequences::48::root:: Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 46, in run
File "/usr/lib/python2.7/site-packages/packstack/plugins/puppet_950.py", line 182, in applyPuppetManifest
File "/usr/lib/python2.7/site-packages/packstack/plugins/puppet_950.py", line 167, in waitforpuppet
File "/usr/lib/python2.7/site-packages/packstack/modules/puppet.py", line 88, in validate_logfile
PuppetError: Error appeared during Puppet run: 192.168.200.144_neutron.pp
Error: Local ip for ovs agent must be set when tunneling is enabled at /var/tmp/packstack/5a69cec4fdee49439d0aef3e7e2f6262/modules/neutron/manifests/agents/ovs.pp:28 on node localhost[0m
You will find full trace in log /var/tmp/packstack/20131021-172048-KfDvFf/manifests/192.168.200.144_neutron.pp.log
Attached are the logs
Attached are the logs
Oct 21 16:54:34 Installed: openstack-packstack-2013.2.1-0.12.dev806.fc20.noarch
Is an ip address configured on CONFIG_NEUTRON_OVS_TUNNEL_IF before running packstack? After packstack fails, is that ip address still configured?
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.