Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When a satellite has x nodes implemented and subsequently removed, the repos remain, and are seen in yum queries across other valid nodes. It is conceivable that this could get unwieldy very quickly.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Register three nodes to parent sat
2. Remove these nodes and register three more
3. yum install <some package> on a child node
Actual results:
[root@hp-dl320egen8-01 ~]# yum install screen
Loaded plugins: product-id, security, subscription-manager
This system is receiving updates from Red Hat Subscription Management.
Katello_Infrastructure_node-certs_cloud-qe-2_idm_lab_bos_redhat_com | 2.9 kB 00:00
Katello_Infrastructure_node-certs_hp-dl320egen8-01_rhts_eng_bos_redhat_com | 2.9 kB 00:00
Katello_Infrastructure_node-certs_ibm-x3250m4-04_lab_eng_rdu2_redhat_com | 2.9 kB 00:00
Katello_Infrastructure_node-certs_ibm-x3550m3-13_lab_eng_brq_redhat_com | 2.9 kB 00:00
Katello_Infrastructure_node-certs_mgmt12_rhq_lab_eng_bos_redhat_com | 2.9 kB 00:00
Katello_Infrastructure_node-certs_mgmt12_rhq_lab_eng_bos_redhat_com/primary_db | 2.7 kB 00:00
Katello_Infrastructure_node-certs_mgmt8_rhq_lab_eng_bos_redhat_com | 2.9 kB 00:00
Katello_Infrastructure_node-certs_mgmt8_rhq_lab_eng_bos_redhat_com/primary_db | 2.7 kB 00:00
This, despite:
[root@mgmt2 ~]# katello -u admin -p admin node list
-----------------------------------------------------------------------------------------------------------------------------------------
Node List
ID Name Environments
-----------------------------------------------------------------------------------------------------------------------------------------
4 hp-dl320egen8-01.rhts.eng.bos.redhat.com Katello Infrastructure: [Library,DEV,QA,GA]
5 mgmt12.rhq.lab.eng.bos.redhat.com Katello Infrastructure: [Library,DEV,QA,GA]
6 mgmt8.rhq.lab.eng.bos.redhat.com Katello Infrastructure: [Library,DEV,QA,GA]
Expected results:
We should probably remove whatever repos are there and getting spread across nodes, if the repos are no longer valid/useful. If a user has a bunch of nodes, and then, say, gets a big hardware refresh and no longer needs the old nodes, all the stale repo stuff remains for those old nodes. Yes, the can probably be removed manually but that could be annoying.
Additional info:
Reason for moving to 6.0.4:
we don't currently create capsule cert repos since we can't upload RPMS via the api/cli currently.
This functionality is likely to return, so this bug will probably become applicable again the future.
Description of problem: When a satellite has x nodes implemented and subsequently removed, the repos remain, and are seen in yum queries across other valid nodes. It is conceivable that this could get unwieldy very quickly. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Register three nodes to parent sat 2. Remove these nodes and register three more 3. yum install <some package> on a child node Actual results: [root@hp-dl320egen8-01 ~]# yum install screen Loaded plugins: product-id, security, subscription-manager This system is receiving updates from Red Hat Subscription Management. Katello_Infrastructure_node-certs_cloud-qe-2_idm_lab_bos_redhat_com | 2.9 kB 00:00 Katello_Infrastructure_node-certs_hp-dl320egen8-01_rhts_eng_bos_redhat_com | 2.9 kB 00:00 Katello_Infrastructure_node-certs_ibm-x3250m4-04_lab_eng_rdu2_redhat_com | 2.9 kB 00:00 Katello_Infrastructure_node-certs_ibm-x3550m3-13_lab_eng_brq_redhat_com | 2.9 kB 00:00 Katello_Infrastructure_node-certs_mgmt12_rhq_lab_eng_bos_redhat_com | 2.9 kB 00:00 Katello_Infrastructure_node-certs_mgmt12_rhq_lab_eng_bos_redhat_com/primary_db | 2.7 kB 00:00 Katello_Infrastructure_node-certs_mgmt8_rhq_lab_eng_bos_redhat_com | 2.9 kB 00:00 Katello_Infrastructure_node-certs_mgmt8_rhq_lab_eng_bos_redhat_com/primary_db | 2.7 kB 00:00 This, despite: [root@mgmt2 ~]# katello -u admin -p admin node list ----------------------------------------------------------------------------------------------------------------------------------------- Node List ID Name Environments ----------------------------------------------------------------------------------------------------------------------------------------- 4 hp-dl320egen8-01.rhts.eng.bos.redhat.com Katello Infrastructure: [Library,DEV,QA,GA] 5 mgmt12.rhq.lab.eng.bos.redhat.com Katello Infrastructure: [Library,DEV,QA,GA] 6 mgmt8.rhq.lab.eng.bos.redhat.com Katello Infrastructure: [Library,DEV,QA,GA] Expected results: We should probably remove whatever repos are there and getting spread across nodes, if the repos are no longer valid/useful. If a user has a bunch of nodes, and then, say, gets a big hardware refresh and no longer needs the old nodes, all the stale repo stuff remains for those old nodes. Yes, the can probably be removed manually but that could be annoying. Additional info: