Bug 1661401 - When upstream product name and product content name are modified, Satellite will only update the product/repository name but won't update the product/repository label.
Summary: When upstream product name and product content name are modified, Satellite w...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: vijsingh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-21 06:43 UTC by Hao Chang Yu
Modified: 2022-03-13 16:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-18 15:15:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Hao Chang Yu 2018-12-21 06:43:55 UTC
Description of problem:

Previously, Satellite didn't update the product/repository name when the upstream contents are changed. Bug 1570792 fixed this issue but the product label and the repository label are still not getting updated.

This can cause issue to user who has ISS Satellite and is relying on a script to automate the rpm export/import task.

This is the 3rd party script written by Redhatter to automate the rpm export/import task.
https://github.com/RedHatSatellite/sat6_scripts

It is relying the repository label to perform task and will fail if the repository label of the source and destination repositories don't match

Actual results:
Product and Repository label not getting updated when their name are changed.

Expected results:
Product and Repository label will be updated when their name are changed.

Comment 3 Brad Buckingham 2019-01-18 15:15:21 UTC
Thanks for the bugzilla.

The labels are purposely immutable for any resource that has one defined.  If the label were to change, it would have numerous impacts both internally and to clients of the Satellite.  For example, they are used for identifying locations of content on filesystems; therefore, changes would impact every client accessing that content.  At this time, there are no plans to alter this; therefore, closing the bugzilla.  If there are concerns, please feel free to re-open and it can be classified as an RFE for consideration.


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