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.

This was fixed upstream in https://github.com/cockpit-project/cockpit/pull/11574 and released in version 192.

@Martin, I have tested the version which include https://github.com/cockpit-project/cockpit/pull/11574, but I think there is still some issues, so I think Bug 1652959 still can not be passed at this moment.I also have left the comments there.

Thanks Yunming. I leave solving bug 1652959 to Katerina, she is currently working on refining the OS vendor/name selection (I don't think that by itself is sufficient, but it's a step towards making this stricter). I hope we can still get that into 8.1.0 final, but by that time this 8.0.0.z backport may not make sense any more as it's too late. Let's just keep this open for now and re-evaluate once we have a fix in 8.1.

FWIW, I don't think this is a major blocker -- there's an obvious workaround (and also the proper solution) by setting the OS vendor/name.

According to the #3 and #4, move the status to ASSIGNED for tracking purpose.

Dropping this 8.0 z-stream bug. 1652959 still isn't completely fixed for 8.1.