Project

General

Profile

Actions

Bug #9274

closed

Config Groups not carried over when cloning a Host Group

Added by Bryan Kearney over 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Host groups
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1187260
Description of problem:
When cloning a Host Group, Config Groups are not carried over to the clone

Version-Release number of selected component (if applicable):
satellite-6.0.6

Steps to Reproduce:
1. Create Host Group with a Config Grou
2. Clone the Host Group
3. Do note that the clone does not have any Config Groups assigned.


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #7407: Cloning a hostgroup do not clone Puppet classes and parametersClosedTom Caspy09/11/2014Actions
Actions #1

Updated by Dominic Cleal over 9 years ago

  • Category set to Host groups
  • Assignee deleted (Ohad Levy)
Actions #2

Updated by The Foreman Bot over 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2145 added
  • Pull request deleted ()
Actions #3

Updated by Tom Caspy over 9 years ago

  • Assignee set to Tom Caspy
Actions #4

Updated by Dominic Cleal over 9 years ago

  • Translation missing: en.field_release set to 32
Actions #5

Updated by Tom Caspy over 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #6

Updated by Dominic Cleal over 9 years ago

  • Related to Bug #7407: Cloning a hostgroup do not clone Puppet classes and parameters added
Actions

Also available in: Atom PDF