Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2122261 - Cloned Host Group do not clone all details from source Host Group.
Summary: Cloned Host Group do not clone all details from source Host Group.
Keywords:
Status: CLOSED DUPLICATE of bug 2058713
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Group
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-29 15:40 UTC by Akshay Kapse
Modified: 2023-09-27 09:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-27 09:22:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Akshay Kapse 2022-08-29 15:40:29 UTC 
Description of problem:
- Cloned hostgroup do not inherit all the details as in source host group.


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

How reproducible: Always

Steps to Reproduce:
- Create a hostgroup and fill all the details.
- Clone this hostgroup and save it.


Actual results:
1) Source hostgroup:
# hammer hostgroup info --name hg1
Id:                    1
Name:                  hg1
Title:                 hg1
Description:           
  
Network:               
    Domain: <domain-name>
Operating system:      
    Architecture:     x86_64
    Operating System: RHEL 8.5
    PXE Loader:       PXELinux BIOS
Parameters:            
    kt_activation_keys => ak1
Locations:             
    GSS
Organizations:         
    RedHat
OpenSCAP Proxy:        1
Content View:          
    Id:   1
    Name: Default Organization View
Lifecycle Environment: 
    Id:   1
    Name: Library


2) Cloned hostgroup:
# hammer hostgroup info --name hg1_c
Id:                    2
Name:                  hg1_c
Title:                 hg1_c
Description:           
  
Network:               
    Domain: <domain-name>
Operating system:      
    Architecture:     x86_64
    Operating System: RHEL 8.5
    PXE Loader:       PXELinux BIOS
Parameters:            
    kt_activation_keys => ak1
Locations:             
    GSS
Organizations:         
    RedHat
OpenSCAP Proxy:        1
Content View:          
    Id:   
    Name:
Lifecycle Environment: 
    Id:   
    Name:


Expected results:
- Cloned hostgroup should inherit all details.
Comment 1 Brad Buckingham 2022-09-01 14:27:38 UTC 
Is this a regression from Satellite 6.11?
Comment 3 Sayan Das 2023-02-19 15:16:19 UTC 
This continues to exist in 6.13 as well.
Comment 4 Brad Buckingham 2023-09-01 21:10:52 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 5 Adam Ruzicka 2023-09-27 09:22:01 UTC 
This looks like a duplicate of BZ #2058713. If you feel the two are different enough to be treated separately, feel free to reopen.

*** This bug has been marked as a duplicate of bug 2058713 ***
Note You need to log in before you can comment on or make changes to this bug.