Bug 1073550

Summary: Change foreman-installer to use openstack-puppet-modules
Product: Red Hat OpenStack Reporter: Martin Magr <mmagr>
Component: openstack-foreman-installerAssignee: Jason Guiditta <jguiditt>
Status: CLOSED ERRATA QA Contact: Omri Hochman <ohochman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.0CC: aortega, derekh, morazi, rhos-maint, yeylon
Target Milestone: z4Keywords: ZStream
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-foreman-installer-1.0.6-1.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1063982 Environment:
Last Closed: 2014-05-29 20:31:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1063980, 1063982    
Bug Blocks:    

Description Martin Magr 2014-03-06 16:52:23 UTC
+++ This bug was initially created as a clone of Bug #1063982 +++

+++ This bug was initially created as a clone of Bug #1063980 +++

Packstack should not use it's own Puppet modules and use modules from openstack-puppet-modules instead.

--- Additional comment from Martin Magr on 2014-02-12 09:20:35 EST ---



--- Additional comment from Lon Hohberger on 2014-02-20 13:26:30 EST ---

devel_ack+ for bug in POST

Comment 2 Martin Magr 2014-03-06 16:54:28 UTC
Apologies, description should be: Foreman installer should not use Packstack's Puppet modules ...

Comment 9 Omri Hochman 2014-05-05 17:43:52 UTC
Verified with openstack-foreman-installer-1.0.6-2.el6ost.noarch -->
having openstack-puppet-modules-2013.2-9.el6ost.noarch installed

looking at puppet.conf:
modulepath     = /etc/puppet/environments/development/modules:/usr/share/openstack-foreman-installer/puppet/modules:/usr/share/openstack-puppet/modules

Comment 11 errata-xmlrpc 2014-05-29 20:31:25 UTC
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/RHSA-2014-0517.html