Description of problem: Web UI report or the search filter in content hosts page to list all the hosts on which the particular repository is enabled. Currently satellite contents the data that which repositories are enabled on the host, we can find it in the "repository sets" tab of content host. But there is no way to get the list of all the hosts on which a particular repository is enabled. Version-Release number of selected component (if applicable): satellite 6.4 Additional info: Workaround Below query helps to get that. # sudo su - postgres -c "psql -d candlepin -c 'select cp_consumer.name from cp_consumer INNER JOIN (select * from cp_content_override where content_label = '\''rh-gluster-3-for-rhel-7-server-rpms'\'' and value = '\''1'\'') x ON x.consumer_id = cp_consumer.id;'" Note - before running the above command on satellite server please change rh-gluster-3-for-rhel-7-server-rpms as per the repository you want to search for.
The query in the description seems to only query overrides for repositories, not the current state. For instance, if a repository is on by default (no override necessary) it does not seem to appear in the query. I believe we need to query the information uploaded from clients by the enabled repositories yum plugin. Is that possible?
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 one month's time. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
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. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact your Red Hat Account Team. Thank you.
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.
Created redmine issue https://projects.theforeman.org/issues/34711 from this bug
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34711 has been resolved.
Verified in 6.11 snap 18.5 on RHEL 7 User can search for Content Hosts based on which repositories they are entitled to. Steps to Reproduce: 1. Sync RHEL 7 server, create cv with repo, and create an activation key with that cv 2. Create a content host from the ak above 3. On the host run: yum repolist all 4. Go to Hosts > Content Hosts 5. Search: repository = "Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server" Expected Result: Host from step 2 appears in the result. Actual Result: Host from step 2 appears in the result. Notes: Step 3 is required so that the repositories enabled on the host are updated and then reflected in Satellite. You could also do something like yum update instead. However, this could cause issues for repositories like kickstart that don't get updated on the host. However, I think that is outside the scope of this use case, as users will only need to know hosts with repositories where they can actually use the content from it.
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 (Moderate: Satellite 6.11 Release), 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/RHSA-2022:5498