Bug 1267692 - Host clone should include associated Puppet classes
Summary: Host clone should include associated Puppet classes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: Christine Fouant
QA Contact: jcallaha
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-30 17:11 UTC by Christine Fouant
Modified: 2019-06-13 21:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 15:57:02 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 8521 0 None None None 2016-04-22 16:58:50 UTC
Red Hat Product Errata RHBA-2015:2474 0 normal SHIPPED_LIVE Satellite 6.1.4 bug fix update 2015-11-19 20:45:48 UTC

Description Christine Fouant 2015-09-30 17:11:57 UTC
As of @1.6.3@, cloning a host does not duplicate it's included classes.  It would be very convient when provisioning multiple hosts if there was a mechanism to clone an existing host that encompassed config groups, included classes, and host level parameters.

Comment 1 Christine Fouant 2015-09-30 17:11:59 UTC
Created from redmine issue http://projects.theforeman.org/issues/8521

Comment 5 jcallaha 2015-11-04 18:44:30 UTC
Verified. Puppet classes are now included in cloned host groups.

  RELEASE: Red Hat Enterprise Linux Server release 7.1 (Maipo)
  FOREMAN: 1.7.2
SATELLITE: 6.1.4
     RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux]
   PUPPET: 3.6.2

Comment 9 errata-xmlrpc 2015-11-19 15:57:02 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.

https://access.redhat.com/errata/RHBA-2015:2474


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