Red Hat Bugzilla – Bug 1466425
Can not disable Red Hat provided repository orphaned after manifest refresh
Last modified: 2017-07-03 10:23:47 EDT
Description of problem:
Gluster 3.2 was erroneously released in Gluster 3.1 repository.
Release engineering fixed this by moving the 3.2 content to the Gluster 3 repository, see https://projects.engineering.redhat.com/browse/RCM-545 .
After refreshing the manifest in Satellite 6.2.10, the new Gluster 3 repository is available, but the previously synchronised Gluster 3.1 repository is no longer listed at Content -> Red Hat repositories, and therefore can not be disabled.
# hammer repository-set info --id 4406 --product-id 48
Name: Red Hat Gluster Storage 3 Server (RPMs)
GPG Key: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
1) ID: 583
Name: Red Hat Gluster Storage 3.1 Server RPMs x86_64 7Server
# hammer repository-set disable --id 4406 --product-id 48 --releasever 7Server --basearch x86_64
Could not disable repository:
Repository not found
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Refresh manifest after repository changes
2. Try disabling the former repository
Repository can not be disabled
Repository can be disabled
*** This bug has been marked as a duplicate of bug 1344391 ***