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.
Hello IBM, will you help with verifying this bug on SCSI/zFCP or NVMe disks?
Comment 2Hanns-Joachim Uhl
2020-07-09 09:10:53 UTC
(In reply to Jan Stodola from comment #1)
> Hello IBM, will you help with verifying this bug on SCSI/zFCP or NVMe disks?
.
... yes, IBM will do fix verification on s390x ... setting OtherQA ...
------- Comment From tstaudt.com 2020-08-21 04:31 EDT-------
for the records ... the bug report from IBM
IBM Bug 186656 - RH1854110- RHEL8.3 Pre-Beta - RHEL8.3 installation not able to create partition in NVMe SSD on s390x (anaconda) (-> AppStream)
that was intended to be fixed by this change has been successfully verified:
"
Shu Ming Ho 2020-08-21 03:02:12 CDT
Tried to install RHEL8.3 Snapshot 1.0 into NVMe, it is a success !
Thanks Guys.
"
Thanks!
------- Comment From hosm.com 2020-08-14 11:41 EDT-------
Hi, how is the outlook for the installer in supporting the installation of RHEL into NVMe?
Raising importance as nearing date (early Sept) of deliverables.
Sorry for the rush and inconvenience caused.
------- Comment From hosm.com 2020-08-21 04:02 EDT-------
------- Comment From tstaudt.com 2020-08-21 04:27 EDT-------
Thanks, everyone.
Closing bug.
------- Comment From tstaudt.com 2020-08-26 03:51 EDT-------
Is this maybe fixed already for RHEL 8.3 Snapshot1 through
IBM Bug 186753 - RH1855200- RHEL8.3 Pre-Beta - allow GPT disk label on s390x (for installations on large SCSI/zFCP or NVMe SSD disks on s390x) (anaconda/python-blivet) (-> AppStream)
Red Hat Bug 1855200 - allow GPT disk label on s390x
------- Comment From tstaudt.com 2020-06-05 05:24 EDT-------
The kernel and s390utils parts have been integrated via
Red Hat Bug 1525179 - [IBM 8.3 FEAT] NVMe IPL support on s390x - kernel part
Red Hat Bug 1525178 - [IBM 8.3 FEAT] NVMe IPL support - s390utils/s390-tools part
------- Comment From tstaudt.com 2020-07-07 03:16 EDT-------
The following bug has been opened
IBM Bug 186656 - RH1854110- RHEL8.3 Pre-Beta - RHEL8.3 installation not able to create partition in NVMe SSD on s390x (anaconda)
which seems to indicate that this feature is not implemented as of Pre-Beta.
------- Comment From tstaudt.com 2020-09-17 09:39 EDT-------
Feature successfully verified.
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 (python-blivet bug fix and enhancement update), 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-2020:4728