Bug 1979258 - Cloning hostgroup doesn't clone Lifecycle and content View from the hostgroup in the WebUI and API
Summary: Cloning hostgroup doesn't clone Lifecycle and content View from the hostgroup...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts - Content
Version: 6.9.0
Hardware: All
OS: All
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-05 12:17 UTC by Anand Agrawal
Modified: 2023-07-21 21:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19105 0 None None None 2023-07-21 21:08:54 UTC

Description Anand Agrawal 2021-07-05 12:17:05 UTC
Description of problem:

cloning of hostgroups is not working anymore properly. 

It doesn't clone Lifecycle and content View from the hostgroup

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

How reproducible:
Always

Steps to Reproduce:
1. Create a HostGroup with Lifecycle and content View from the Configure -> Hostgroup
2. Now Clone the above Hostgroup
3. Provide a name to the cloned Hostgroup, you will see Lifecycle and content View field are empty in the cloned Hostgroup

Actual results:
Lifecycle and content View are not copied/cloned to the new Hostgroup

Expected results:
Lifecycle and content View should be copied to the cloned Hostgroup

Additional info:

2021-07-05T08:06:10 [I|app|813f69df] Processing by HostgroupsController#clone as HTML
2021-07-05T08:06:10 [I|app|813f69df]   Parameters: {"id"=>"2-Provision_HG"}
2021-07-05T08:06:10 [I|app|813f69df]   Rendering hostgroups/new.html.erb within layouts/application
2021-07-05T08:06:11 [I|app|813f69df]   Rendered collection of puppetclasses/_selectedClasses.html.erb [0 times] (Duration: 0.0ms | Allocations: 3)
2021-07-05T08:06:11 [I|app|813f69df]   Rendered collection of puppetclasses/_classes_in_groups.html.erb [0 times] (Duration: 0.0ms | Allocations: 3)
:
:
:
2021-07-05T08:06:28 [I|app|ba60efa2] Started POST "/hostgroups" for 10.10.113.74 at 2021-07-05 08:06:28 -0400
2021-07-05T08:06:28 [I|app|ba60efa2] Processing by HostgroupsController#create as HTML
2021-07-05T08:06:28 [I|app|ba60efa2]   Parameters: {"utf8"=>"✓", "authenticity_token"=>"ydzFOFbxZFnbnKmUG4nmd1pz+bBrtjk1dFYsRGXilBr06latENEULVoF9ey1u3GeRmIxsQXF44fxBrxkGQdQeA==", "hostgroup"=>{"parent_id"=>"", "name"=>"andy", "description"=>"", "lifecycle_environment_id"=>"", "content_view_id"=>"", "content_source_id"=>"", "environment_id"=>"1", "compute_resource_id"=>"1", "compute_profile_id"=>"1", "puppet_proxy_id"=>"1", "puppet_ca_proxy_id"=>"1", "openscap_proxy_id"=>"1", "ansible_role_ids"=>[""], "puppetclass_ids"=>[""], "domain_id"=>"2", "subnet_id"=>"1", "realm_id"=>"", "architecture_id"=>"1", "operatingsystem_id"=>"2", "medium_id"=>"", "ptable_id"=>"120", "pxe_loader"=>"PXELinux BIOS", "root_pass"=>"[FILTERED]", "location_ids"=>["", "2"], "organization_ids"=>["", "1"], "id"=>""}, "commit"=>"Submit"}
2021-07-05T08:06:28 [I|aud|ba60efa2] Hostgroup (6) create event on name andy
2021-07-05T08:06:28 [I|aud|ba60efa2] Hostgroup (6) create event on environment_id 1

Comment 1 Brad Buckingham 2021-07-08 14:24:50 UTC
Is this a regression from Satellite 6.8?

Comment 2 Anand Agrawal 2021-07-08 14:34:33 UTC
(In reply to Brad Buckingham from comment #1)
> Is this a regression from Satellite 6.8?

Yes, I think this is a regression for Satellite 6.8

Regards,
Anand

Comment 5 Brad Buckingham 2023-07-21 21:06:39 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.


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