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.

Bug 2032507

Summary: move fdasd, lszdev and vmcp into s390utils-core package for 8.4 [rhel-8.4.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: s390utilsAssignee: Dan Horák <dhorak>
Status: CLOSED ERRATA QA Contact: Vilém Maršík <vmarsik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.4CC: aos-bugs, chanphil, christian.lapolt, danili, dhorak, dslavens, fleber, Holger.Wolf, jcajka, krmoser, psundara, rvr
Target Milestone: rcKeywords: Reopened, Triaged, ZStream
Target Release: ---Flags: pm-rhel: mirror+
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: s390utils-2.15.1-5.el8_4.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2032486 Environment:
Last Closed: 2022-04-20 16:19:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2032486    
Bug Blocks: 2031637    

Comment 1 Dan Horák 2021-12-14 16:41:09 UTC 
- fdasd and lszdev moved to core in 8.5.0 via the rebase to 2.16.0 in bug #1919241
- vmcp is moving to core in 8.6.0 via bug #2021071
Comment 2 Prashanth Sundararaman 2021-12-16 15:33:04 UTC 
Dan,

Any updates. i would like to get this package available before next week because RHCOS pipelines are also going to be shutdown for the holidays.

Thanks
Prashanth
Comment 3 Dan Horák 2021-12-16 15:48:52 UTC 
Officially this can go out on January 25th when the Batch Update 6 has GA. But a build will be available earlier and a commit even before that. We are tied to the RHEL processes ...
Comment 4 Prashanth Sundararaman 2021-12-16 18:21:51 UTC 
ok. In the meantime, do you think we can work around it by using the s390utils-core-2.16.0-2.el8.s390x.rpm to build rhcos for 4.10 which is based off rhel 8.4? would it cause any issues?
Comment 5 Dan Horák 2021-12-17 09:41:43 UTC 
(In reply to Prashanth Sundararaman from comment #4)
> ok. In the meantime, do you think we can work around it by using the
> s390utils-core-2.16.0-2.el8.s390x.rpm to build rhcos for 4.10 which is based
> off rhel 8.4? would it cause any issues?

I believe using the s390utils-core-2.16.0-2.el8.s390x.rpm will be OK, there are no incompatible changes AFAIK.
Comment 6 Vilém Maršík 2022-02-03 11:16:41 UTC 
Looks good:
DISTRO=RHEL-8.4.0-updates-20211026.0
# for A in fdasd lszdev vmcp; do echo -n "$A : ";rpm -qf `which $A `; done
fdasd : s390utils-base-2.15.1-5.el8.s390x
lszdev : s390utils-base-2.15.1-5.el8.s390x
vmcp : s390utils-base-2.15.1-5.el8.s390x
# rpm -qa | grep s390utils
s390utils-core-2.15.1-5.el8.s390x
s390utils-base-2.15.1-5.el8.s390x
# rpm -U s390utils-base-2.15.1-5.el8_4.3.s390x.rpm s390utils-core-2.15.1-5.el8_4.3.s390x.rpm
# for A in fdasd lszdev vmcp; do echo -n "$A : ";rpm -qf `which $A `; done
fdasd : s390utils-core-2.15.1-5.el8_4.3.s390x
lszdev : s390utils-core-2.15.1-5.el8_4.3.s390x
vmcp : s390utils-core-2.15.1-5.el8_4.3.s390x
Comment 9 Prashanth Sundararaman 2022-02-03 17:21:50 UTC 
can we get this tested ASAP so it can be added to the advisory before March? we need to pull this into RHCOS.thanks!
Comment 13 Vilém Maršík 2022-02-16 21:20:03 UTC 
No newer build for 8.4.z in Beaker, nothing to do in stage2. Setting verified.
Comment 19 errata-xmlrpc 2022-04-20 16:19:35 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 (s390utils 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-2022:1452