Description of problem: Working with Cisco we ran into an issue which Pradeep from Cisco says was address in the upstream. ---- This is an issue with the upstream stack forge puppet-neutron. There is a recent Change to upstream manifests that added a symlink that isn¹t really needed for modern cisco plugin configuration and causes duplicate definition errors in conjunction with ovs. Here is the recent commit related to this: https://github.com/stackforge/puppet-neutron/commit/4be69d2cdde185a241ecb34 361ab6a473191e975 For now as a workaround, just comment out lines 174-178 from /usr/share/packstack/modules/neutron/manifests/plugins/cisco.pp #file {'/etc/neutron/plugin.ini': # ensure => link, # target => '/etc/neutron/plugins/cisco/cisco_plugins.ini', # require => Package['neutron-plugin-cisco'] #} There is a pending upstream fix that should resolve this next week. I¹ll let you know once the fix lands so you guys can pull the fix in. ~ Prad Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Returning this to A4 for further consideration/discussion.
The point of adding the bug to A5 was that to update the puppet-neutron module we will need to first backport the noted pengding review to stable/havana (if it's not already done) and then test installation with updated module, because module updates tend to break stuff. Noted workaround will be part of A4 o-p-m build of course. But unfortunately I don't think we have resources to do the full update in A4 time frame. Steve, it would also help if you would add url to 'pending upstream fix' to this bug.
Moving it to A5. If we ended up being able to implement it upstream in the A4 timeframe we could move it back.
Update from Pradeep: Hi Steve: The patch for that issue is still pending upstream. Reason for the delay is that its part of a bigger patch. I’ll see if we can break it up so we can get a fix for this symlink issue sooner. Here is link to the review: https://review.openstack.org/#/c/78550/ ~ Pradeep
Pradeep updated , he made a smaller patch covering this issue. I am moving back to A4, if you feel comfortable pulling this smaller patch. If not, understand and move back to A5. ---- Here is the patch I submitted upstream for this issue. https://review.openstack.org/#/c/84728/ Its merged into havana now. You guys should be able to pull it down. ~ Pradeep
Workaround patch added in openstack-puppet-modules-2013.2-8.el6ost
Submitted pull request with update: https://github.com/redhat-openstack/openstack-puppet-modules/pull/9
Tested rpm -q openstack-puppet-modules; openstack-puppet-modules-2013.2-9.el6ost.noarch tail -10 /usr/share/openstack-puppet/modules/neutron/manifests/plugins/cisco.pp } # In RH, this link is used to start Neutron process but in Debian, it's used only # to manage database synchronization. ensure_resource('file', '/etc/neutron/plugin.ini', { ensure => link, target => '/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini', require => Package['neutron-plugin-ovs'] }) } [root@puma33 bin]# tail -10 /usr/share/openstack-puppet/modules/neutron/manifests/plugins/ovs.pp } # In RH, this link is used to start Neutron process but in Debian, it's used only # to manage database synchronization. file {'/etc/neutron/plugin.ini': ensure => link, target => '/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini', require => Package['neutron-plugin-ovs'] } } [root@p
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0577.html