This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2058713 - Cloning Host Group doesn't copy data under Host Group tab
Summary: Cloning Host Group doesn't copy data under Host Group tab
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Group
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2122261 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-25 17:02 UTC by Griffin Sullivan
Modified: 2024-06-06 11:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 11:33:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-20435 0 None Migrated None 2024-06-06 11:33:35 UTC

Description Griffin Sullivan 2022-02-25 17:02:32 UTC 
Description of problem:
When you clone a Host Group, the data under the first tab "Host Group" doesn't copy over. This includes lifecycle environment, CV, Content Source, etc. I'm not sure if this is expected behavior since the other tabs copy data correctly, but the term clone implies all data would be copied over.

Version-Release number of selected component (if applicable):
7.0.0 but also observed in 6.10.3

How reproducible:
100%

Steps to Reproduce:
1. Create a host group and fill out as much as you want 
2. Clone the host group

Actual results:
None of the data on the "Host Group" tab is carried over to the clone.

Expected results:
All of the data from the first Host Group is copied to the new one.
Comment 1 Sayan Das 2022-02-26 07:34:58 UTC 
I have noticed something similar for a very specific scenario i.e. for inherited hostgroups. 

There is a parent HG present where I have selected certain values.

There is a Child HG created which is inheriting all possible values from parent HG and also has the blank fields filled up manually. To test, I also changed one of the inherited values to something else.

Now, if I clone the Child HG, It gives me the form to modify and save the cloned HG but All the preselected values are directly being inherited from Parent HG instead of actually having the exact same set of data\selection cloned from the Child HG and that is not exactly expected.

Cloning should retain all data and selection from the source hostgroup even if the source has a parent.


The same behavior exists on Sat 6.10 as well.
Comment 3 Brad Buckingham 2023-03-06 11:40:19 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 4 Sayan Das 2023-03-06 12:33:22 UTC 
This bug is valid for 6.13 as well. This should definitely be fixed i.e. Cloning an HG should properly retain the selected data from the source host group.
Comment 6 Brad Buckingham 2023-04-06 17:10:05 UTC 
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Comment 7 Brad Buckingham 2023-04-06 17:19:41 UTC 
The closure in comment 6 was unintentional as we planned to leave this open based upon comment 4.  Sayan, thanks for noticing this mistake!
Comment 8 Adam Ruzicka 2023-09-27 09:22:01 UTC 
*** Bug 2122261 has been marked as a duplicate of this bug. ***
Comment 9 Eric Helms 2024-06-06 11:33:36 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.