Description of problem: Packstack installation while trying to apply cinder puppet modules: "modules/cinder/manifests/setup_test_volume.pp:34; cannot redeclare at" Version-Release number of selected component (if applicable): OSP 8 How reproducible: 100% Steps to Reproduce: 1. Deploy OpenStack using Packstack Actual results: 192.168.1.14_cinder.pp: [ ERROR ] 08:04:11 Applying Puppet manifests [ ERROR ] 08:04:11 08:04:11 ERROR : Error appeared during Puppet run: 192.168.1.14_cinder.pp 08:04:11 Error: Duplicate declaration: File[/var/lib/cinder] is already declared in file /var/tmp/packstack/61680f7e39ce45faa0fb3b4bbabc41f8/modules/cinder/manifests/setup_test_volume.pp:34; cannot redeclare at /var/tmp/packstack/61680f7e39ce45faa0fb3b4bbabc41f8/manifests/192.168.1.14_cinder.pp:101 on node... Expected results: Installation completed successfully
Attachinf here Emilien Macchi's answer to the e-mail I've sent to rh-openstack-dev: Commits that are related to this error: https://github.com/openstack/puppet-cinder/commit/a8b991f6bebf770efe34c67d8bbea7b092db0000 https://github.com/openstack/packstack/commit/ac8dc735a3e0f06e7ed7a1dff6ce7122cc1210fb I suspect a missing packaging update here.
We need the following commits to be included: https://review.openstack.org/325925 <- apply to openstack-puppet-modules https://review.openstack.org/327666 <- apply to packstack
Change in https://review.openstack.org/327666 is merged so new packstack from stable/liberty can be packaged. This must be pushed to repow with the newest version of OPM in stable/liberty, 7.1.1.
This is indeed fixed in opm 7.1.1 upstream in rdo. If it is ok to rebase osp8 to this, I can do so. I am going to clone this now and see if we can get acks to pull it in.
*** Bug 1344677 has been marked as a duplicate of this bug. ***
I don't know if it's the same issue (the error is not), but we also have a problem with 9 release: https://bugzilla.redhat.com/show_bug.cgi?id=1346823
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. https://access.redhat.com/errata/RHBA-2016:1354