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.
Bug 1381123 - s390x standby memory automatically onlined after boot [rhel-7.3.z]
Summary: s390x standby memory automatically onlined after boot [rhel-7.3.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: s390x
OS: Linux
urgent
high
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Branislav Blaškovič
Marc Muehlfeld
URL:
Whiteboard:
: 1381942 (view as bug list)
Depends On: 1370161 1381885
Blocks: 1399073
TreeView+ depends on / blocked
 
Reported: 2016-10-03 07:19 UTC by Marcel Kolaja
Modified: 2019-12-16 06:58 UTC (History)
14 users (show)

Fixed In Version: systemd-219-30.el7_3.1
Doc Type: Bug Fix
Doc Text:
Previously, the udev device manager automatically enabled all memory banks on IBM z System installations. As a consequence, hot plug memory was enabled automatically, which was incorrect. With this update, system architecture checks have been added to the udev rules to address the problem. As a result, hot plug memory is no longer automatically enabled.
Clone Of: 1370161
Environment:
Last Closed: 2016-11-04 08:56:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 148233 0 None None None 2016-11-28 09:05:10 UTC
Red Hat Product Errata RHSA-2016:2610 0 normal SHIPPED_LIVE Moderate: systemd security and bug fix update 2016-11-03 15:50:26 UTC

Description Marcel Kolaja 2016-10-03 07:19:33 UTC 
This bug has been copied from bug #1370161 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 5 Marcel Kolaja 2016-10-05 12:01:32 UTC 
*** Bug 1381942 has been marked as a duplicate of this bug. ***
Comment 8 Hanns-Joachim Uhl 2016-10-13 08:05:23 UTC 
Hello Red Hat / Lukas,
quick question ...
.
there are the following related bugs available:
.
RHBZ bug 1370161 - s390x standby memory automatically onlined after boot 
... fixed in RHEL7.3 RC ...
RHBZ bug 1375603 - s390x standby memory automatically onlined after boot [rhel-7.2.z] 
... which is the related 7.2.z zstream bug for RHBZ 1370161 ...
RHBZ bug 1381123 - s390x standby memory automatically onlined after boot [rhel-7.3.z]
... which is the related 7.3.z zstream bug for RHBZ 1370161 and which is 
this bugzilla ...
.
... now my question:
why is this 7.3.z zstream bugzilla 1381123 still needed
if the original issue is fixed already in RHEL7.3 RC through bug 1370161 ...?
Please advise ...
Thanks for your support.
Comment 9 Lukáš Nykrýn 2016-10-13 08:16:39 UTC 
We found out that the original fix was not enough.

Originally we only had:
https://github.com/lnykryn/systemd-rhel/commit/195083a33b4204d513787e7f4b6c63f19a0fe1c7

The 7.3.z. also contains
https://github.com/lnykryn/systemd-rhel/commit/48e2af5667e67a7a7f58eb17aaf5349379b2484a
Comment 10 Hanns-Joachim Uhl 2016-10-13 09:19:30 UTC 
(In reply to Lukáš Nykrýn from comment #9)
> We found out that the original fix was not enough.
> 
> Originally we only had:
> https://github.com/lnykryn/systemd-rhel/commit/
> 195083a33b4204d513787e7f4b6c63f19a0fe1c7
> 
> The 7.3.z. also contains
> https://github.com/lnykryn/systemd-rhel/commit/
> 48e2af5667e67a7a7f58eb17aaf5349379b2484a
.
... thanks for the information ...
Comment 14 errata-xmlrpc 2016-11-04 08:56:07 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://rhn.redhat.com/errata/RHSA-2016-2610.html
Note You need to log in before you can comment on or make changes to this bug.