Actions
Bug #8521
closed
Host clone should include associated Puppet classes
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
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.
Updated by Dominic Cleal over 10 years ago
- Project changed from Smart Proxy to Foreman
- Category changed from Core to Host creation
Are those classes directly included, and does the new host show the same Puppet environment?
Updated by Dominic Cleal over 10 years ago
- Subject changed from ability to clone a host INCLUDING it's included classes to Host clone should include associated Puppet classes
Updated by Dominic Cleal over 10 years ago
- Related to Bug #7407: Cloning a hostgroup do not clone Puppet classes and parameters added
Updated by David Schmitt over 10 years ago
The classes are directly included and may have contained fqdn matched smart parameters.
The cloned host shows the same hostgroup.
Updated by Dominic Cleal almost 10 years ago
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
Updated by The Foreman Bot almost 10 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2588 added
- Pull request deleted (
)
Updated by Dominic Cleal over 9 years ago
- Related to Bug #9815: HostGroup Clone doesn't work if the hostgroup has parameters added
Updated by Marek Hulán over 9 years ago
- Translation missing: en.field_release set to 63
Updated by Dominic Cleal over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset f1a2c1407b161ea51d9be579f8973ff1fc0ebce8.
Updated by
Actions