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.
DescriptionRAD team bot copy to z-stream
2019-10-28 09:03:06 UTC
This bug has been copied from bug #1712768 and has been proposed to be backported to 7.7 z-stream (EUS).
Comment 4Hanns-Joachim Uhl
2019-11-13 08:45:38 UTC
Hello Red Hat / Karel,
... would it be possible that you provide us the updated rpm "util-linux-2.23.2-61.el7_7.1"
for our early testing ...?
If this would be possible, please provide the rpm _for 390x_ ...
... please advise.
Thanks in advance for your support.
(In reply to Hanns-Joachim Uhl from comment #4)
> If this would be possible, please provide the rpm _for 390x_ ...
Sure, unofficial and for testing only (src and 390 rpms): http://people.redhat.com/kzak/bz1766091/
Look forward for your feedback, thanks.
Comment 6Hanns-Joachim Uhl
2019-11-15 12:07:11 UTC
(In reply to Karel Zak from comment #5)
> (In reply to Hanns-Joachim Uhl from comment #4)
> > If this would be possible, please provide the rpm _for 390x_ ...
>
> Sure, unofficial and for testing only (src and 390 rpms):
> http://people.redhat.com/kzak/bz1766091/
>
> Look forward for your feedback, thanks.
.
Hello Red Hat / Karel,
... thanks for the rpms ... but you only provided the 's390' rpms ...
... please also provide the 's390x' rpms for our testing ...
Thanks in advance for your support.
------- Comment From hannsj_uhl.com 2019-11-20 05:42 EDT-------
(In reply to comment #11)
> Ah, sorry. The s390x rpms provided too.
Comment from Michael Finnegan 2019-11-19 18:23:10 CST
For s390x verify
No lsmem User process faults reported since installing
util-linux-2.23.2-61.el7_7.1.s390x
Thanks
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-2019:3983