-
Bug
-
Resolution: Not a Bug
-
Normal
-
rhel-10.0.beta
-
No
-
Moderate
-
rhel-sst-installer
-
ssg_front_door
-
13
-
3
-
False
-
-
No
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
-
s390x
-
None
What were you trying to do that didn't work?
Creating a disk image by running anaconda on an installed system is failing on s390x with the following error:
[root@s390x-kvm-101 ~]# anaconda --image /root/disk.img --kickstart ks.cfg Starting installer, one moment... failed to load module s390: libbd_s390.so.3: cannot open shared object file: No such file or directory 05:52:48 Enforcing the non-interactive text mode for dir and image installations. libreport is not available in this environment - bug reporting disabled anaconda 40.22.3.9-1.el10 for anaconda bluesky (pre-release) started. 05:52:49 Service org.fedoraproject.Anaconda.Modules.Storage has failed to start: Process org.fedoraproject.Anaconda.Modules.Storage exited with status 1 [root@s390x-kvm-101 ~]#
A workaround is to install the libblockdev-s390 package manually.
Please provide the package NVR for which bug is seen:
RHEL-10.0-20240811.0
anaconda-40.22.3.9-1.el10
python-blivet-3.10.0-5.el10
libblockdev-3.1.0-6.el10
How reproducible:
Always on s390x
Steps to reproduce
- dnf install anaconda
- qemu-img create /root/disk.img 10G
- touch /root/ks.cfg
- anaconda --image /root/disk.img --kickstart /root/ks.cfg
Expected results
anaconda starts successfully (and fails to continue due to an empty kickstart file)
Actual results
Error and anaconda fails:
failed to load module s390: libbd_s390.so.3: cannot open shared object file: No such file or directory
