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 1025344 - cli: Attempting to disable a promoted repo does not return a complete error context.
Summary: cli: Attempting to disable a promoted repo does not return a complete error c...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: sthirugn@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-31 14:12 UTC by Corey Welton
Modified: 2019-09-26 18:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:24:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Corey Welton 2013-10-31 14:12:47 UTC 
Description of problem:
When a user tries to disable a repo that has been promoted, this fails - but the fail message is incomplete, it is missing the context/reason.

Version-Release number of selected component (if applicable):
Satellite-6.0.2-RHEL-6-20131030.0

How reproducible:


Steps to Reproduce:
1.  Sync AND promote RHEL content in org "Katello Infrastructure"
2.  katello --user admin --password admin product repository_set_disable --org "Katello Infrastructure" --name "Red Hat Enterprise Linux Server" --set_name "Red Hat Enterprise Linux 6 Server (RPMs)"
3.  view results.

Actual results:
Repository disable [ Red Hat Enterprise Linux 6 Server (RPMs) ] failed.:


Expected results:
Repository disable [ Red Hat Enterprise Linux 6 Server (RPMs) ] failed.:  Cannot disable promoted content.  Please perform a content deletion changeset before disabling this repo.

(or something similar)


Additional info:
Comment 3 Brad Buckingham 2014-06-25 21:19:36 UTC 
Although much has changed in both API/CLI since this bug was introduced, need to confirm it is an issue in the current implementation.
Comment 4 Brad Buckingham 2016-04-13 16:22:56 UTC 
I am no longer seeing the behavior described on Satellite 6.2 beta snap 7; therefore, moving the bug to ON_QA for verification.

hammer> repository-set available-repositories --organization "Default Organization" --product "Red Hat Enterprise Linux Server" --name "Red Hat Enterprise Linux 7 Server (Kickstart)"
----------------------------------------------|--------|---------|---------------|--------
NAME                                          | ARCH   | RELEASE | REGISTRY NAME | ENABLED
----------------------------------------------|--------|---------|---------------|--------
Red Hat Enterprise Linux 7 Server (Kickstart) | x86_64 | 7.0     |               | no     
Red Hat Enterprise Linux 7 Server (Kickstart) | x86_64 | 7.1     |               | no     
Red Hat Enterprise Linux 7 Server (Kickstart) | x86_64 | 7.2     |               | yes    
----------------------------------------------|--------|---------|---------------|--------

hammer> repository-set disable --organization "Default Organization" --product "Red Hat Enterprise Linux Server" --name "Red Hat Enterprise Linux 7 Server (Kickstart)" --name "Red Hat Enterprise Linux 7 Server (Kickstart)" --releasever "7.2" --basearch x86_64
Could not disable repository:
  Repository cannot be deleted since it has already been included in a published Content View. Please delete all Content View versions containing this repository before attempting to delete it.
hammer>
Comment 5 sthirugn@redhat.com 2016-04-13 16:25:49 UTC 
Verified as per Comment 4.
Comment 7 Bryan Kearney 2016-07-27 11:24:57 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.