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.

Starting with rhel-7.5 criu will be available for s390x and needs to be
added to the rhel-7.5 product listing.
Please also add criu to the rhel-alt-7.5 product listing for aarch64 and
s390x.
rhel-7.5 s390x: https://bugzilla.redhat.com/show_bug.cgi?id=1456513
rhel-alt-7.5 s390x: https://bugzilla.redhat.com/show_bug.cgi?id=1457955
rhel-alt-7.5 aarch64: https://bugzilla.redhat.com/show_bug.cgi?id=1464596

Adrian via Lubos

(originally reported as RCM-21637) I'll keep separate request for alt and rhel

Hi Adrian, we're missing pm_ack here. Let me get it.

Lubos

Thanks!

Hello Adrian,

since the errata was created today (but it's more about the build attach time to the advisory) you'll need to wait for upcoming nightly to take.

So just click on reload filelists tomorrow and you should see s390x. I did check config and all is in place.

Lubos

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/RHEA-2018:0700