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.
Description of problem:
Using the same kickstart file as in RHEL8 (just updating the URL of the source version) - the dbginfo.sh is no longer installed, as s390utils-base is no longer a default package installed automatically.
Version-Release number of selected component (if applicable):
all RHEL 9 versions
How reproducible:
reuse a RHEL8 kickstart file and just update the URL:
sample content from our packages section is:
%packages
@core
%end
Steps to Reproduce:
1. copy and update the URL - diff to viusualize the simple update
# diff kickstart_rhel8.ks kickstart_rhel9.ks
< url --url "http://<mirror>/redhat/s390x/RHEL8.8-latest/DVD"
---
> url --url "http://<mirror>/redhat/s390x/RHEL9.1-latest/DVD"
2. install RHEL8
virt-install --reinstall testle8 --memory 4096 --vcpus 2 --disk /var/lib/libvirt/images/rhel8_dvd.qcow2 --location http://<mirror>/redhat/s390x/RHEL8.8-latest/DVD --initrd-inject "/root/kickstart_rhel8.ks" --extra-args "inst.ks=file:///kickstart_rhel8.ks"
3. install RHEL9
virt-install --reinstall testle9 --memory 4096 --vcpus 2 --disk /var/lib/libvirt/images/rhel9_dvd.qcow2 --location http://<mirror>/redhat/s390x/RHEL9.1-latest/DVD --initrd-inject "/root/kickstart_rhel9.ks" --extra-args "inst.ks=file:///kickstart_rhel9.ks"
4. see different results of "yum list --installed | grep s390utils"
RHEL8:
s390utils-base.s390x 2:2.25.0-2.el8 @anaconda
s390utils-core.s390x 2:2.25.0-2.el8 @anaconda
RHEL9:
s390utils-core.s390x 2:2.22.0-2.el9 @anaconda
Actual results:
customers are installing now systems without needed debug tools
Expected results:
debug tools are essential in case of any error and need to be installed already with the initilal installation as done in previous RHEL versions.
Additional info:
s390utils-base seems to be only included in a "STANDARD" installation of RHEL9, but many instructions and setup methods are using kickstart files for customizing.
The purpose of the @core group is to install a minimal functional system and with newer RHEL releases we are trying to make it smaller. It's not a supported RHEL installation, for that you need the @standard group, which includes the s390utils-base package with dbginfo.sh. The proper solution is to update the kickstart file if you want to use the @core group.
Hello Dan, as this packing is done by RedHat and not by IBM, i readdress this bug to RH. I confirmed that IBM is delivering a complete git repo and no splitting to this packages is doen by us.
Please forward to the packing team and we are glad to help resorting the packages. Thx !
There is not much to do from the packaging point of view. If someone is intentionally using the @core group via a kickstart file, then it has some consequences (not supported, minimal, etc). The dbginfo.sh script requires other tools from the base subpackage including the ones written in perl. And perl is simply a no-go for @core (it translates to CoreOS and other minimal environments). My recommendation would be to update the documentation that suggests to use kickstarts with just @core.
(In reply to siglen from comment #4)
> dbginfo.sh does not use perl, but i found that tar seems to be replaced by
> gzip as default.
dbginfo.sh calls tools written in perl, eg. ziorep_config, but generally it needs all the "s390-tools" to be available, which means all of s390utils-base ...
Description of problem: Using the same kickstart file as in RHEL8 (just updating the URL of the source version) - the dbginfo.sh is no longer installed, as s390utils-base is no longer a default package installed automatically. Version-Release number of selected component (if applicable): all RHEL 9 versions How reproducible: reuse a RHEL8 kickstart file and just update the URL: sample content from our packages section is: %packages @core %end Steps to Reproduce: 1. copy and update the URL - diff to viusualize the simple update # diff kickstart_rhel8.ks kickstart_rhel9.ks < url --url "http://<mirror>/redhat/s390x/RHEL8.8-latest/DVD" --- > url --url "http://<mirror>/redhat/s390x/RHEL9.1-latest/DVD" 2. install RHEL8 virt-install --reinstall testle8 --memory 4096 --vcpus 2 --disk /var/lib/libvirt/images/rhel8_dvd.qcow2 --location http://<mirror>/redhat/s390x/RHEL8.8-latest/DVD --initrd-inject "/root/kickstart_rhel8.ks" --extra-args "inst.ks=file:///kickstart_rhel8.ks" 3. install RHEL9 virt-install --reinstall testle9 --memory 4096 --vcpus 2 --disk /var/lib/libvirt/images/rhel9_dvd.qcow2 --location http://<mirror>/redhat/s390x/RHEL9.1-latest/DVD --initrd-inject "/root/kickstart_rhel9.ks" --extra-args "inst.ks=file:///kickstart_rhel9.ks" 4. see different results of "yum list --installed | grep s390utils" RHEL8: s390utils-base.s390x 2:2.25.0-2.el8 @anaconda s390utils-core.s390x 2:2.25.0-2.el8 @anaconda RHEL9: s390utils-core.s390x 2:2.22.0-2.el9 @anaconda Actual results: customers are installing now systems without needed debug tools Expected results: debug tools are essential in case of any error and need to be installed already with the initilal installation as done in previous RHEL versions. Additional info: s390utils-base seems to be only included in a "STANDARD" installation of RHEL9, but many instructions and setup methods are using kickstart files for customizing.