Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
So that it's clear, this issue hits a specific feature in RHEL8 Cockpit, which allows users to see available updates for a system. As it is, this features is effectively broken due to this, as it takes many minutes for an end user to get any information. Most users will just assume the feature is broken, or stop using it, as 'yum check-update' will return an answer many minutes faster.
(In reply to Richard Hughes from comment #4)
> This is by design, enabled_metadata=0 will prevent that behavior for the
> .repo file. It's been this way for about 4 years, and see this link for the
> rationalle
> https://blogs.gnome.org/hughsie/2015/01/09/finding-hidden-applications-with-
> gnome-software/
Aha, then, hm, I guess this is a subscription-manager issue then. The end-user problem is Cockpit taking 9 minutes to see if there are software updates :)
> The option is called enabled_metadata, not enable_metadata -- I've commented on thesubman bug to this affect too.
I'll close this one as PK is doing exactly as it should do.