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.
Two months ago Cockpit introduced a new "Software Updates" page for "classic" RPM (and deb) based systems [1]. So far we have only had a "Software Updates" page on Atomic based systems (cockpit-ostree).
This has been improved and matured since then (user testing, subscription detection, etc.) and has been shipped in Fedora 26, Debian and Ubuntu stable releases, so it did get some field testing. I think it is mature enough to get included into RHEL Extras now.
Note that the UI will grow in the future, e. g. to add support for configuring automatic updates or exposing repository information (see the spec [2]). As with the rest of cockpit in extras this package would see frequent rebases and thus deliver these new features.
[1] http://cockpit-project.org/blog/cockpit-143.html
[2] https://github.com/cockpit-project/cockpit/wiki/Feature:-System-Updates-for-dnf,-yum,-apt-hosts
Comment 6Oneata Mircea Teodor
2017-09-07 13:54:13 UTC
@Oneata, the point of this is to release a subpackage in rhel 7.4 extras, not 7.5 or 7.5 extras. Because this is not a new package, just releasing a subpackage that we were previously filtering out with whitelists, we've gotten the ok to do this.
Comment 8Oneata Mircea Teodor
2017-09-07 14:10:02 UTC
(In reply to Peter from comment #7)
> @Oneata, the point of this is to release a subpackage in rhel 7.4 extras,
> not 7.5 or 7.5 extras. Because this is not a new package, just releasing a
> subpackage that we were previously filtering out with whitelists, we've
> gotten the ok to do this.
OK than, no process for extra zstream. If you have a QE assigned request the ack from him for qa_ack.
I'll provide ack for 7.4z after.
Jan, can you please review this and set the QA ack? This new package is covered by our CI, and I'm happy to answer any questions about it (on IRC or here) wrt. what it does, how to test it manually, etc.
Comment 10Djordje Todorovic
2017-09-08 12:21:42 UTC
@toneata,
Hello sir, we have the qa_ack+. Can you please review and give us official 7.4z blessing.
Thanks!
Comment 11Oneata Mircea Teodor
2017-09-08 12:24:58 UTC
(In reply to Djordje Todorovic from comment #10)
> @toneata,
>
> Hello sir, we have the qa_ack+. Can you please review and give us official
> 7.4z blessing.
>
> Thanks!
Hello,
Done.
Comment 12Djordje Todorovic
2017-09-08 13:35:28 UTC
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, 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/RHBA-2017:2961