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 2213447 - Remove API for changing content view + lifecycle environment organizations
Summary: Remove API for changing content view + lifecycle environment organizations
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Samir Jha
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-08 07:51 UTC by Shweta Singh
Modified: 2023-08-16 15:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 15:27:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36680 0 Normal New Remove API for changing content view + lifecycle environment organizations 2023-08-15 02:35:51 UTC
Red Hat Issue Tracker SAT-18437 0 None None None 2023-06-15 14:31:36 UTC

Description Shweta Singh 2023-06-08 07:51:16 UTC 
Description of problem:
Missing support to update organization in a content-view and lifecycle-environment through Web UI. Same is present via hammer.

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

How reproducible:
Always

Steps to Reproduce:
1.Navigate to Web UI and create a content-view or a lifecycle-environment
2.Create an organization 
3.Try to update content-view or lifecycle-environment with new organization through UI.

Actual results:
We don't have option to update the organization through UI but same is available via hammer.

Expected results:
We should be able to update organization through any interface and it will more user-friendly.

Additional info:
Comment 3 Ian Ballou 2023-06-12 14:56:01 UTC 
I'm guessing that changing a CVs org doesn't update things like the distribution path -- so we shouldn't be allowing this at all. I'd recommend that we first deprecate the API and then remove it in the next Katello release.
Comment 4 Ian Ballou 2023-06-12 14:59:34 UTC 
Not only would the distribution paths be wrong, but the related repositories would also not exist, causing all sorts of CV-related errors.  Changing the title.
Comment 5 Samir Jha 2023-08-14 16:41:53 UTC 
Created redmine issue https://projects.theforeman.org/issues/36680 from this bug
Comment 6 Samir Jha 2023-08-15 02:36:40 UTC 
Hi Shweta,

The organization-id params in hammer commands when updating CV or env or other records are present to allow for scoping search of the resource by name to provided organization. The organization itself is not updated/affected if you pass a new value to it as it's not an update param for the call, rather a search param to locate the resource. The Org id is needed for these calls to support searching by name or label on different resources which generally are unique only to an organization. If you use Id of resource to target a resource, the organization-id is ignored by the API as id is a sufficient unique identifier for resources. I'd consider this expected behavior as hammer doesn't allow changing org id on resources just like UI/API.

If that makes sense, let me know if we can close this out or if you needed some further action on this.
Comment 8 Samir Jha 2023-08-16 15:27:02 UTC 
Thanks Shweta,

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