Bug 2025119 - --label is rejected by hammer organization update command
Summary: --label is rejected by hammer organization update command
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Organizations and Locations
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Shweta Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-19 23:10 UTC by Jessica Hanley
Modified: 2023-07-21 21:06 UTC (History)
5 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)

Description Jessica Hanley 2021-11-19 23:10:24 UTC
Description of problem:

hammer does not update organization's label to given value. 

[root@moya69v:~/ 15:17:25] $ hammer organization list
---|-------|-------|-------------|------
ID | TITLE | NAME  | DESCRIPTION | LABEL
---|-------|-------|-------------|------
1  | MYORG | MYORG |             | MYORG
---|-------|-------|-------------|------
[root@moya69v:~/ 16:03:30] $ hammer organization update --id 1 --label "new-label"
Could not update the organization:
  Label cannot be changed.

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

Satellite 6.9

How reproducible:

every time


Steps to Reproduce:
1.  run the hammer command to change the label of an organization

Actual results:

The hammer command rejects any attempt to update an Organization's label.


Expected results:

The hammer command should rename an Organization's label.


Additional info:

My guess is that the reason this hasn't been fixed thus far is that the organization label is reflected in the directory structure at "/var/lib/pulp/published/yum/https/repos/ORGANIZATION".  However, this should be resolvable by creating a soft link at "/var/lib/pulp/published/yum/https/repos/new-label" to the old location, and then updating the database.

Comment 2 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.