Mock Environment Kickstart for rocky-8-xfce-fc+elrepo.iso

Happy New Year to all !

References:

1) “Kickstart for rocky-8-xfce-fc+elrepo.iso".

2) “Run install from within mock shell # 706“, issue opened by hroncok.


Hi Nazunalika:

The original .iso, as per Reference #1, was created last February, using livecd-
creator. This time around, based on Rocky-8.9, I want to use your standard
mock procedure to generate an up-to-date version.

The initial attempt with mock, using the original .ks file, failed with the
message:
The following mandatory spokes are not completed:
Installation source
Software Selection


I came across Reference #2, and I don’t understand its contents entirely, but it
seems to claim that yum install commands do not work in a mock environment.

The %post section at the end of the original .ks file contains 2 such commands.

I would appreciate your analysis and commentary on Reference #2, and if
such commands are a problem, a workaround prescription from you.

Thanks !

Len E.

You’ll need to analyze the anaconda logs to determine why your kickstart is not working. Without any information to go off of (logs, in particular), no one will be able to assist you.

Your reference to the github issue is completely unrelated to your issue. Your issue stems from anaconda not liking what is in your kickstart and it is up to you to determine why that is. All anaconda logs will be in the mock root.

Reference:

“Anaconda fails to install from kickstart with: …".
https://bugzilla.redhat.com/show_bug.cgi?id=1911300


Hi Nazunalika:

Thanks to your advice, I was able to locate 2 very helpful log files in directory
/var/lib/mock/rocky-8-x86_64/root/builddir/anaconda:
anaconda.log and dbus.log.

In the dbus.log specifically, the failure problem was characterized as an
“UnavailableModuleError”.

With that information, I was able to search the web and come up with the reference
above, which describes the problem exactly.


The reference mentions a possible workaround in terms of increasing the service_
start_timeout value from 600000ms to 1800000ms.

Accordingly, I reran your standard mock procedure with the following amendment:

-In the mock --install command, I inserted the anaconda and nano packages.
(I’m more familiar with nano than vim-minimal).

-After entering the mock shell, the pwd command confirmed that the normal
/default working directory is /builddir.
-Then, cd /usr/share/anaconda/dbus, nano anaconda-bus.conf and change
the timeout value to 1800000 ms.
-Then, cd /builddir and run the livemedia-creator command.
The result was the same failure, but after 30 minutes rather than 10 minutes.


My test machine for this run was the HP DC5800 with primarily-Intel controllers.
Immediately after the test failure, I checked the status of the relevant partitions
with gparted:

                                    (Size)                   (Used)                   (Unused)

sda7 --> root                 21GB                  4.14GB                   16.86GB
sda9 --> /home              13GB                  2.24GB                   10.76GB
sda11 --> /var                11GB                  4.35GB                     6.65GB
sda14 --> /boot              520MB              172.73MB               347.27MB
sda8 -->   swap              4GB                     24.65MB                 3.98GB

There seemed to be enough disk space available.

The anaconda.log file is as follows:

23:53:40,865 INF core.configuration.product: Loading information about products from /etc/anaconda/product.d.
23:53:40,866 INF core.configuration.product: Found Scientific Linux at /etc/anaconda/product.d/scientific-linux.conf.
23:53:40,867 INF core.configuration.product: Found Red Hat Virtualization at /etc/anaconda/product.d/rhev.conf.
23:53:40,868 INF core.configuration.product: Found Rocky Linux at /etc/anaconda/product.d/rocky.conf.
23:53:40,868 INF core.configuration.product: Found oVirt Node Next at /etc/anaconda/product.d/ovirt.conf.
23:53:40,869 INF core.configuration.product: Found CentOS Linux at /etc/anaconda/product.d/centos.conf.
23:53:40,869 INF core.configuration.product: Found Fedora Silverblue at /etc/anaconda/product.d/fedora-silverblue.conf.
23:53:40,870 INF core.configuration.product: Found Fedora AtomicHost at /etc/anaconda/product.d/fedora-atomic-host.conf.
23:53:40,871 INF core.configuration.product: Found AlmaLinux at /etc/anaconda/product.d/almalinux.conf.
23:53:40,872 INF core.configuration.product: Found Red Hat Enterprise Linux at /etc/anaconda/product.d/rhel.conf.
23:53:40,872 INF core.configuration.product: Found Fedora Workstation at /etc/anaconda/product.d/fedora-workstation.conf.
23:53:40,873 INF core.configuration.product: Found Fedora Workstation Live at /etc/anaconda/product.d/fedora-workstation-live.conf.
23:53:40,873 INF core.configuration.product: Found Fedora at /etc/anaconda/product.d/fedora.conf.
23:53:40,874 INF core.configuration.product: Found CentOS Stream at /etc/anaconda/product.d/centos-stream.conf.
23:53:40,874 INF core.configuration.product: Found Fedora Server at /etc/anaconda/product.d/fedora-server.conf.
23:53:40,875 INF core.configuration.product: The product Rocky Linux is supported.
23:53:40,884 INF main: /usr/sbin/anaconda 33.16.9.4-1.el8.rocky.0.1
23:53:43,153 INF isys: 2109028 kB (2059 MB) are available
23:53:43,164 INF startup_utils: check_memory(): total:2059, needed:320, graphical:410
23:53:43,165 INF startup_utils: Switching logging level to debug
23:53:43,165 INF main: anaconda called with cmdline = ['/usr/sbin/anaconda', '--kickstart', '/builddir/rocky-8-xfce-customelrepo.ks', '--cmdline', '--loglevel', 'debug', '--dirinstall', '--remotelog', '127.0.0.1:39177']
23:53:43,166 INF main: Default encoding = utf-8 
23:53:43,167 INF misc: Writing a temporary configuration loaded from: ['/etc/anaconda/anaconda.conf', '/etc/anaconda/product.d/rhel.conf', '/etc/anaconda/product.d/rocky.conf', '/etc/anaconda/conf.d/00-do-nothing.conf', '/etc/anaconda/conf.d/01-still-do-nothing.conf']
23:53:43,180 INF core.dbus: Connecting to the Anaconda bus at unix:abstract=/tmp/dbus-WLw6AdO4NQ,guid=866d1a10b295f2d446e91e8b65989687.
00:23:44,357 ERR stdout: Service org.fedoraproject.Anaconda.Modules.Storage has failed to start: Failed to activate service 'org.fedoraproject.Anaconda.Modules.Storage': timed out (service_start_timeout=1800000ms)

The dbus.log file is as follows:
(Showing the end portion only: too many characters in its entirety)


INFO:program:stdout[2]:   LVM version:     2.03.14(2)-RHEL8 (2021-10-20)
  Library version: 1.02.181-RHEL8 (2021-10-20)
  Driver version:  4.46.0
  Configuration:   ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-default-dm-run-dir=/run --with-default-run-dir=/run/lvm --with-default-pid-dir=/run --with-default-locking-dir=/run/lock/lvm --with-usrlibdir=/usr/lib64 --enable-fsadm --enable-write_install --with-user= --with-group= --with-device-uid=0 --with-device-gid=6 --with-device-mode=0660 --enable-pkgconfig --enable-cmdlib --enable-dmeventd --enable-blkid_wiping --with-cluster=internal --enable-cmirrord --with-udevdir=/usr/lib/udev/rules.d --enable-udev_sync --with-thin=internal --with-cache=internal --enable-lvmpolld --enable-lvmlockd-dlm --enable-lvmlockd-dlmcontrol --enable-lvmlockd-sanlock --enable-dbus-service --enable-notify-dbus --enable-dmfilemapd --with-writecache=internal --with-vdo=internal --with-vdo-format=/usr/bin/vdoformat --with-integrity=internal --disable-silent-rules

INFO:program:stderr[2]: 
INFO:program:...done [2] (exit code: 0)
DEBUG:anaconda.modules.common.base.base:Publish the service.
DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Security.
INFO:anaconda.core.dbus:Connecting to the Anaconda bus at unix:abstract=/tmp/dbus-WLw6AdO4NQ,guid=866d1a10b295f2d446e91e8b65989687.
DEBUG:anaconda.modules.common.base.base:Publish the service.
DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Payloads/Packages.
INFO:anaconda.core.dbus:Connecting to the Anaconda bus at unix:abstract=/tmp/dbus-WLw6AdO4NQ,guid=866d1a10b295f2d446e91e8b65989687.
DEBUG:dasbus.connection:Registering a service name org.fedoraproject.Anaconda.Modules.Services.
DEBUG:dasbus.connection:Registering a service name org.fedoraproject.Anaconda.Modules.Security.
DEBUG:blivet:registered device format class LUKS as luks
DEBUG:blivet:registered device format class Integrity as integrity
DEBUG:blivet:registered device format class LVMPhysicalVolume as lvmpv
DEBUG:blivet:registered device format class MDRaidMember as mdmember
DEBUG:blivet:registered device format class MultipathMember as multipath_member
DEBUG:blivet:registered device format class PPCPRePBoot as prepboot
dbus-daemon[8705]: Successfully activated service 'org.fedoraproject.Anaconda.Modules.Services'
DEBUG:anaconda.modules.boss.module_manager.start_modules:Service org.fedoraproject.Anaconda.Modules.Services started successfully.
DEBUG:anaconda.modules.boss.module_manager.start_modules:org.fedoraproject.Anaconda.Modules.Services is available.
DEBUG:anaconda.modules.common.base.base:Start the loop.
DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Payloads.
DEBUG:dasbus.connection:Registering a service name org.fedoraproject.Anaconda.Modules.Payloads.
dbus-daemon[8705]: Successfully activated service 'org.fedoraproject.Anaconda.Modules.Security'
DEBUG:anaconda.modules.boss.module_manager.start_modules:Service org.fedoraproject.Anaconda.Modules.Security started successfully.
DEBUG:anaconda.modules.common.base.base:Start the loop.
dbus-daemon[8705]: Successfully activated service 'org.fedoraproject.Anaconda.Modules.Payloads'
DEBUG:anaconda.modules.boss.module_manager.start_modules:org.fedoraproject.Anaconda.Modules.Security is available.
DEBUG:anaconda.modules.boss.module_manager.start_modules:Service org.fedoraproject.Anaconda.Modules.Payloads started successfully.
DEBUG:anaconda.modules.boss.module_manager.start_modules:org.fedoraproject.Anaconda.Modules.Payloads is available.
DEBUG:anaconda.modules.common.base.base:Start the loop.
DEBUG:anaconda.modules.common.base.base:Publish the service.
DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Users.
INFO:anaconda.core.dbus:Connecting to the Anaconda bus at unix:abstract=/tmp/dbus-WLw6AdO4NQ,guid=866d1a10b295f2d446e91e8b65989687.
DEBUG:blivet:registered device format class SwapSpace as swap
DEBUG:blivet:registered device format class StratisBlockdev as stratis
INFO:program:Running... udevadm trigger --action=change --subsystem-match=block
DEBUG:dasbus.connection:Registering a service name org.fedoraproject.Anaconda.Modules.Users.
dbus-daemon[8705]: Successfully activated service 'org.fedoraproject.Anaconda.Modules.Users'
DEBUG:anaconda.modules.boss.module_manager.start_modules:Service org.fedoraproject.Anaconda.Modules.Users started successfully.
DEBUG:anaconda.modules.boss.module_manager.start_modules:org.fedoraproject.Anaconda.Modules.Users is available.
DEBUG:anaconda.modules.common.base.base:Start the loop.
INFO:dasbus.connection:Connecting to the system bus.
INFO:dasbus.connection:Connecting to the system bus.
WARNING:dasbus.connection:Connection can't be created:
g-io-error-quark: Could not connect: No such file or directory (1)
DEBUG:anaconda.modules.network.nm_client:get new NM Client failed: SystemBus connection check failed.
DEBUG:anaconda.modules.network.network:Applying boot options <pyanaconda.core.kernel.KernelArguments object at 0x7fd08a6dd0f0>
DEBUG:anaconda.modules.common.base.base:Publish the service.
DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Network/Firewall.
INFO:anaconda.core.dbus:Connecting to the Anaconda bus at unix:abstract=/tmp/dbus-WLw6AdO4NQ,guid=866d1a10b295f2d446e91e8b65989687.
DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Network.
DEBUG:dasbus.connection:Registering a service name org.fedoraproject.Anaconda.Modules.Network.
dbus-daemon[8705]: Successfully activated service 'org.fedoraproject.Anaconda.Modules.Network'
DEBUG:anaconda.modules.boss.module_manager.start_modules:Service org.fedoraproject.Anaconda.Modules.Network started successfully.
DEBUG:anaconda.modules.boss.module_manager.start_modules:org.fedoraproject.Anaconda.Modules.Network is available.
DEBUG:anaconda.modules.common.base.base:Start the loop.
DEBUG:program:Return code: 0
INFO:program:Running... udevadm settle --timeout=300
DEBUG:program:Return code: 0
WARNING:py.warnings:/usr/lib64/python3.6/site-packages/pyanaconda/core/util.py:33: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
  import imp

INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/langtable/data/languages.xml.gz' 0x7f807a113ef0>
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/langtable/data/languages.xml.gz' 0x7f30359dbf60>
INFO:blivet:failed to get initiator name from iscsi firmware: storaged iSCSI functionality not available
DEBUG:anaconda.modules.storage.bootloader.bootloader:The default type is set to 'BootloaderType.DEFAULT'.
DEBUG:anaconda.modules.storage.fcoe.fcoe:Start up the FCoE module.
INFO:program:Running... modprobe libfc
INFO:program:stderr:
INFO:program:b'modprobe: FATAL: Module libfc not found in directory /lib/modules/4.18.0-513.5.1.el8_9.x86_64'
DEBUG:program:Return code: 1
DEBUG:anaconda.modules.storage.iscsi.iscsi:Start up the iSCSI module.
DEBUG:anaconda.modules.storage.zfcp.zfcp:Start up the zFCP module.
INFO:program:Running [3] e2fsck -V ...
INFO:program:stdout[3]: 
INFO:program:stderr[3]: e2fsck 1.45.6 (20-Mar-2020)
	Using EXT2FS Library version 1.45.6, 20-Mar-2020

INFO:program:...done [3] (exit code: 0)
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/langtable/data/keyboards.xml.gz' 0x7f30359dbf98>
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/langtable/data/keyboards.xml.gz' 0x7f807a113dd8>
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/langtable/data/timezones.xml.gz' 0x7f30359dbf60>
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/langtable/data/timezones.xml.gz' 0x7f807a113f28>
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/langtable/data/timezoneidparts.xml.gz' 0x7f30359dbf98>
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/langtable/data/timezoneidparts.xml.gz' 0x7f807a113ef0>
DEBUG:blivet:               Ext4FS.supported: supported: True ;
DEBUG:blivet:get_format('ext4') returning Ext4FS instance with object id 0
DEBUG:blivet:            Ext4FS.supported: supported: True ;
DEBUG:blivet:trying to set new default fstype to 'ext4'
DEBUG:blivet:                  Ext4FS.supported: supported: True ;
DEBUG:blivet:get_format('ext4') returning Ext4FS instance with object id 1
DEBUG:blivet:               Ext4FS.supported: supported: True ;
INFO:program:Running... lsblk --bytes -a -o NAME,SIZE,OWNER,GROUP,MODE,FSTYPE,LABEL,UUID,PARTUUID,MOUNTPOINT
INFO:program:stdout:
INFO:program:NAME            SIZE OWNER GROUP MODE       FSTYPE LABEL UUID PARTUUID MOUNTPOINT
INFO:program:loop0     6444548096 root  root  brw-rw-rw-                            /mnt/sysimage
INFO:program:sda     320072933376                                                   
INFO:program:|-sda1   32218389504                                                   
INFO:program:|-sda2    1073741824                                                   
INFO:program:|-sda3  162014429184                                                   
INFO:program:|-sda4          1024                                                   
INFO:program:|-sda5   16525557760                                                   
INFO:program:|-sda6   17716740096                                                   
INFO:program:|-sda7   22548578304                                                   /proc/filesystems
INFO:program:|-sda8    4294967296                                                   [SWAP]
INFO:program:|-sda9   13958643712                                                   
INFO:program:|-sda10  11811160064                                                   
INFO:program:|-sda11  11811160064                                                   /var/cache/dnf
INFO:program:|-sda12  11585716224                                                   
INFO:program:|-sda13  13957595136                                                   
INFO:program:`-sda14    545259520                                                   
INFO:program:sr0       4700372992                                                   
DEBUG:program:Return code: 0
DEBUG:blivet:lsblk output:
NAME            SIZE OWNER GROUP MODE       FSTYPE LABEL UUID PARTUUID MOUNTPOINT
loop0     6444548096 root  root  brw-rw-rw-                            /mnt/sysimage
sda     320072933376                                                   
|-sda1   32218389504                                                   
|-sda2    1073741824                                                   
|-sda3  162014429184                                                   
|-sda4          1024                                                   
|-sda5   16525557760                                                   
|-sda6   17716740096                                                   
|-sda7   22548578304                                                   /proc/filesystems
|-sda8    4294967296                                                   [SWAP]
|-sda9   13958643712                                                   
|-sda10  11811160064                                                   
|-sda11  11811160064                                                   /var/cache/dnf
|-sda12  11585716224                                                   
|-sda13  13957595136                                                   
`-sda14    545259520                                                   
sr0       4700372992                                                   

DEBUG:blivet:lvm filter: clearing the lvm devices list
DEBUG:blivet:lvm filter: clearing the lvm devices list
DEBUG:blivet:trying to set new default fstype to 'xfs'
DEBUG:blivet:                XFS.supported: supported: True ;
INFO:program:Running... modprobe --dry-run xfs
INFO:program:stderr:
INFO:program:b'modprobe: FATAL: Module xfs not found in directory /lib/modules/4.18.0-513.5.1.el8_9.x86_64'
DEBUG:program:Return code: 1
DEBUG:blivet:Kernel module xfs not available
DEBUG:blivet:get_format('xfs') returning XFS instance with object id 2
DEBUG:blivet:                          XFS.supported: supported: False ;
DEBUG:blivet:invalid default fstype (xfs): XFS instance (0x7f6fc32d8a90) object id 2--
  type = xfs  name = xfs  status = False
  device = None  uuid = None  exists = False
  options = defaults
  create_options = None  supported = False  formattable = True  resizable = False
  mountpoint = None  mountopts = 
  label = None  size = 0 B  target_size = 0 B

DEBUG:blivet:                           XFS.supported: supported: False ;
Traceback (most recent call last):
  File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/__main__.py", line 29, in <module>
    service = StorageService()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/storage.py", line 138, in __init__
    self._set_storage(create_storage())
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/devicetree/model.py", line 51, in create_storage
    return InstallerStorage()
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/storage/devicetree/model.py", line 69, in __init__
    self.set_default_fstype(conf.storage.file_system_type or self.default_fstype)
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blivet/blivet.py", line 1179, in set_default_fstype
    self._check_valid_fstype(newtype)
  File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/blivet/blivet.py", line 1164, in _check_valid_fstype
    raise ValueError("new value %s is not valid as a default fs type" % newtype)
ValueError: new value xfs is not valid as a default fs type
DEBUG:anaconda.modules.common.base.base:Publish the service.
DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Timezone.
INFO:anaconda.core.dbus:Connecting to the Anaconda bus at unix:abstract=/tmp/dbus-WLw6AdO4NQ,guid=866d1a10b295f2d446e91e8b65989687.
DEBUG:dasbus.connection:Registering a service name org.fedoraproject.Anaconda.Modules.Timezone.
dbus-daemon[8705]: Successfully activated service 'org.fedoraproject.Anaconda.Modules.Timezone'
DEBUG:anaconda.modules.boss.module_manager.start_modules:Service org.fedoraproject.Anaconda.Modules.Timezone started successfully.
DEBUG:anaconda.modules.boss.module_manager.start_modules:org.fedoraproject.Anaconda.Modules.Timezone is available.
DEBUG:anaconda.modules.common.base.base:Start the loop.
DEBUG:anaconda.modules.common.base.base:Publish the service.
DEBUG:dasbus.connection:Publishing an object at /org/fedoraproject/Anaconda/Modules/Localization.
INFO:anaconda.core.dbus:Connecting to the Anaconda bus at unix:abstract=/tmp/dbus-WLw6AdO4NQ,guid=866d1a10b295f2d446e91e8b65989687.
DEBUG:dasbus.connection:Registering a service name org.fedoraproject.Anaconda.Modules.Localization.
dbus-daemon[8705]: Successfully activated service 'org.fedoraproject.Anaconda.Modules.Localization'
DEBUG:anaconda.modules.common.base.base:Start the loop.
DEBUG:anaconda.modules.boss.module_manager.start_modules:Service org.fedoraproject.Anaconda.Modules.Localization started successfully.
DEBUG:anaconda.modules.boss.module_manager.start_modules:org.fedoraproject.Anaconda.Modules.Localization is available.
dbus-daemon[8705]: Failed to activate service 'org.fedoraproject.Anaconda.Modules.Storage': timed out (service_start_timeout=1800000ms)
INFO:anaconda.threading:Thread Failed: AnaTaskThread-StartModulesTask-1 (139666363774720)
ERROR:anaconda.modules.common.task.task:Thread AnaTaskThread-StartModulesTask-1 has failed: Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/boss/module_manager/start_modules.py", line 143, in _start_service_by_name_handler
    returned = call()
  File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 460, in <lambda>
    lambda: self._get_method_reply(getter),
  File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply
    return self._handle_method_error(error)
  File "/usr/lib/python3.6/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error
    raise exception from None
dasbus.error.DBusError: Failed to activate service 'org.fedoraproject.Anaconda.Modules.Storage': timed out (service_start_timeout=1800000ms)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 280, in run
    threading.Thread.run(self)
  File "/usr/lib64/python3.6/threading.py", line 885, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task.py", line 97, in _task_run_callback
    self._set_result(self.run())
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/boss/module_manager/start_modules.py", line 81, in run
    unavailable.discard(callback())
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/boss/module_manager/start_modules.py", line 138, in <lambda>
    self._callbacks.put(lambda: self._start_service_by_name_handler(*args, **kwargs))
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/boss/module_manager/start_modules.py", line 147, in _start_service_by_name_handler
    ) from error
pyanaconda.modules.common.errors.module.UnavailableModuleError: Service org.fedoraproject.Anaconda.Modules.Storage has failed to start: Failed to activate service 'org.fedoraproject.Anaconda.Modules.Storage': timed out (service_start_timeout=1800000ms)

INFO:anaconda.threading:Thread Done: AnaTaskThread-StartModulesTask-1 (139666363774720)
WARNING:dasbus.server.handler:The call org.fedoraproject.Anaconda.Task.Finish has failed with an exception:
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/dasbus/server/handler.py", line 421, in _method_callback
    *unwrap_variant(parameters)
  File "/usr/lib/python3.6/site-packages/dasbus/server/handler.py", line 234, in _handle_call
    return handler(*parameters)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task_interface.py", line 114, in Finish
    self.implementation.finish()
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task.py", line 161, in finish
    threadMgr.raise_if_error(self._thread_name)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 171, in raise_if_error
    raise exc_info[0](exc_info[1]).with_traceback(exc_info[2])
  File "/usr/lib64/python3.6/site-packages/pyanaconda/threading.py", line 280, in run
    threading.Thread.run(self)
  File "/usr/lib64/python3.6/threading.py", line 885, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/common/task/task.py", line 97, in _task_run_callback
    self._set_result(self.run())
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/boss/module_manager/start_modules.py", line 81, in run
    unavailable.discard(callback())
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/boss/module_manager/start_modules.py", line 138, in <lambda>
    self._callbacks.put(lambda: self._start_service_by_name_handler(*args, **kwargs))
  File "/usr/lib64/python3.6/site-packages/pyanaconda/modules/boss/module_manager/start_modules.py", line 147, in _start_service_by_name_handler
    ) from error
pyanaconda.modules.common.errors.module.UnavailableModuleError: Service org.fedoraproject.Anaconda.Modules.Storage has failed to start: Failed to activate service 'org.fedoraproject.Anaconda.Modules.Storage': timed out (service_start_timeout=1800000ms)
DEBUG:anaconda.modules.boss.module_manager.module_manager:Stop modules.
DEBUG:dasbus.connection:Disconnecting from the bus.

Hi Nazunalika:

I ran a mock test on one of my other machines, the HP Pavilion Media Centre
m8247c which has the sata disk controllers, and encountered a different problem.

The mock run fails at the Installation Source/Software selection stage, with the
anaconda.log file containing the following error message:

16:59:42,127 ERR payload.manager: PayloadError: Failed to download metadata for repo 'Fedora29-media': Cannot download
 repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

The message seems illogical, because, when the yum list kernel kernel-*
command is entered from a lxterminal or Mate-terminal session, because
the Fedora29 kernel is a “higher” version than the Rocky-8.9 kernel, all the
Fedora29 kernel packages are listed as available, with no problem, which
demonstrates that there is nothing wrong with the repo metadata.

Similarly, because the Fedora27 Graphics packages are a “lower” version than
the standard Rocky-8.9 graphics packages, the command
yum list xorg-x11-server-Xorg-1.19.6-7.fc27.x86_64, with the explicit version
number, shows that the package is available from the Fedora27-media repo.


The .repo files in /etc/yum.repos.d are as follows:


[Fedora29-media]
name=Fedora29-media repo
baseurl=file:///run/media/user/Fedora29+27/Fedora29
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-x86_64



[Fedora27-media]
name=Fedora27-media repo
baseurl=file:///run/media/user/Fedora29+27/Fedora27
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-x86_64

I used your standard mock command sequence with the one alteration to the
mock -r install command:

kmod -sata_nv-3.5-9.el8_9.elrepo.x86_64.rpm
kmod-forcedeth-0.0-10.el8_9.elrepo.x86_64.rpm inserted in front of
lorax-lmc-novirt


As a separate test, I converted both of the above repos to local repositories
on disk, but the change made no difference.

Len E.

Hi Nazunalika:

Since my previous submission on this problem on Jan. 7, I tried several things
without coming up with a solution, but I believe I now have a very clear definition
of the problem.

From my previous work on os-prober, I’ve learned that the major libraries in
Fedora versions fc31 through fc34 are compatible with those in Rocky-8, whereas
Fedora-35 initiated the use of the library upgrades which have been used for
RHEL-9 and derivatives.

With no success on Rocky-8.9, I ran some mock tests on Fedora-32, Fedora-33,
and Fedora-34 LXDE installations, also with no success. They all use earlier
earlier versions of mock than Rocky-8, but they do have .cfg and .tpl files in place
for rocky-8, EPEL-8, and rocky+epel-8.


Since my test of mock on my HP DC5800 machine which I reported on my
Jan. 5 submission, the situation had regressed whereby additional tests always
failed with the error that the rocky-8 BaseOS repodata was unreadable. Changing
the reference in the .repo file from mirrors to baseurl didn’t help. Yesterday, I
changed the reference in Rocky-BaseOS.repo in /etc/yum.repos.d and in the
rocky-8.tpl file specifically to https://mirrors.rit.edu, a mirror that has been
very reliable for many years. The test failed again, but the dbus.log information
was a revelation.


The following is the first of 2 excerpts from the dbus.log file:

DEBUG:anaconda.modules.storage.bootloader.bootloader:The default type is set to 'BootloaderType.DEFAULT'.
DEBUG:anaconda.modules.storage.fcoe.fcoe:Start up the FCoE module.
INFO:program:Running... modprobe libfc
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/lan
gtable/data/languages.xml.gz' 0x7f07db9052b0>
INFO:root:reading file=<gzip _io.BufferedReader name='/usr/lib/python3.6/site-packages/lan
gtable/data/languages.xml.gz' 0x7f99dc00b7f0>
INFO:program:stderr:
INFO:program:b'modprobe: FATAL: Module libfc not found in directory /lib/modules/4.18.0-51
3.11.1.el8_9.x86_64'
DEBUG:program:Return code: 1
DEBUG:anaconda.modules.storage.iscsi.iscsi:Start up the iSCSI module.

Mock is trying to activate the Fibre Channel on Ethernet (FCOE) capability and
failing on not finding library libfc. This same error occurred on all the Fedora-
based tests also. It makes no sense that this capability is being activated when
the fcoe kernel module is not installed. The only kernel that had it installed was
on Fedora 33, and the same failure occurred anyway.

It turns out that this particular content was present in my Jan. 5 submission also,
but I was too preoccupied with the timeout consideration and missed its
significance.

The only reference to libfc that I was able to find anywhere was by searching on
the web for “Working with Kernel Modules :: Fedora Docs”.

The following excerpt is from that document:

You can load the Fibre Channel over Ethernet module verbosely by typing the following at a shell prompt:
~]# modprobe -v fcoe
insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko.xz
insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/libfc/libfc.ko.xz
insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko.xz
insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko.xz

The 2nd excerpt from the dbus.log file is as follows:

DEBUG:blivet:lvm filter: clearing the lvm devices list
DEBUG:blivet:lvm filter: clearing the lvm devices list
DEBUG:blivet:trying to set new default fstype to 'xfs'
DEBUG:blivet:                XFS.supported: supported: True ;
INFO:program:Running... modprobe --dry-run xfs
INFO:program:stderr:
INFO:program:b'modprobe: FATAL: Module xfs not found in directory /lib/modules/4.18.
0-513.11.1.el8_9.x86_64'
DEBUG:program:Return code: 1
DEBUG:blivet:Kernel module xfs not available
DEBUG:blivet:get_format('xfs') returning XFS instance with object id 2
DEBUG:blivet:                          XFS.supported: supported: False ;
DEBUG:blivet:invalid default fstype (xfs): XFS instance (0x7f51e9e28c50) object id 2
--
  type = xfs  name = xfs  status = False
  device = None  uuid = None  exists = False
  options = defaults
  create_options = None  supported = False  formattable = True  resizable = False
  mountpoint = None  mountopts = 
  label = None  size = 0 B  target_size = 0 B

This error also came up on the Fedora-base mock runs.
I was able to overcome it by adding two packages to the mock --install command
in front of lorax-lmc-novirt:
libguestfs-xfs xfsprogs

The libfc problem still prevented a successful completion.


I believe there is something inherently wrong in the mock package which causes
the libfc problem.
If you agree with my assessement, and with your approval, I would follow up
with a bug report submission to EPEL.

Please advise.
Len E.

Hi Nazunalika:

Given the problems I reported on my HP DC5800 test machine on Jan. 18, I
resumed testing on my HP Pavilion Media Centre HPm8247c machine with
the sata disk controllers, about which I last reported on Jan. 7.

Finally, some good news: I found a way to process the .ks file successfully
using mock.


When the mock package is installed on Rocky, there is no man page associated
with it. Fortunately, one is available from https://linux.die.net/man/1/mock.

Of pivotal interest is the command
mock [options] --copyin path [path …] destination

It allows importing files from external directories into the mock shell.
It is hugely important that if the source is a directory, all the files in it
are imported intact.

This capability allows constructing a very-complete mock environment before
starting the livemedia-creator run.


Tools and Preparation

Given that I have no proficiency whatsoever with bash or shell scripts, I found it
useful to have 2 terminal packages installed to ease the effort and prevent some
confusion with keyboard entry. (I used lxterminal as the primary terminal,
mate-terminal as the secondary terminal). I used the primary terminal for the
entry of the standard mock command sequence, and the secondary terminal for
all other purposes to avoid interrupting the primary terminal command sequence.
It was particularly helpful to highlight and copy some text on the secondary
terminal and then simply paste it into place on the primary terminal.

In the /home directory, I created a livemedia-tools sub-directory containing
the following items:
-the latest rocky-8-xfce-customelrepo.ks
-the actual Fedora29 and Fedora27 directories which have had the
repodata installed with createrepo.
NB: every file in these directories should have ownership set to
user:mock -----> root ownership is not allowed.
-the following keys: RPM-GPG-KEY-EPEL-8,
RPM-GPG-KEY-fedora-27-primary,
RPM-GPG-KEY-fedora-27-x86_64.
RPM-GPG-KEY-fedora-29-primary,
RPM-GPG-KEY-fedora-29-x86_64,
RPM-GPG-KEY-rockyofficial

-from the secondary terminal, cd /home/user/livemedia-tools,
highlight and copy the kickstart name.


Actual mock run: from the primary terminal

During earlier tests, I used the .cfg file, rocky+epel-8-x86_64; I stayed with that.
cd /home/user/livemedia-tools

Follow the standard mock command sequence, with some alterations:

-On the mock --install command, insert the 2 kmod rpm’s, and again, I
added nano, in front of lorax-lmc-novirt

-Before the mock -r rocky+epel-8-x86_64 --shell command,
mock -r rocky+epel-8-x86_64 --copyin RPM-GPG-K* /etc/pki/rpm-gpg,
mock -r rocky+epel-8-x86_64 --copyin Fedora27 /var/lib/rpm
mock -r rocky+epel-8-x86_64 --copyin Fedora29 /var/lib/rpm

-After the mock --shell command,
modprobe sata_nv
modprobe forcedeth
cd /etc/pki/rpm-gpg, rpm --import RPM-GPG-K*

   cd /etc/dnf,        nano dnf.conf
  -to the end of the dnf.conf file, key in the contents of the Fedora27.repo
    and Fedora29.repo files.

-Then, cd /builddir, and enter the standard commands for the livemedia-creator
run.
******************************************************************

The following excerpt show the .repo file contents:

[Fedora27]
name=Fedora27 repo
baseurl=file:///var/lib/rpm/Fedora27
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-27-x86_64




[Fedora29]
name=Fedora29 repo
baseurl=file:///var/lib/rpm/Fedora29
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-x86_64


The following excerpt show the Fedora27 and Fedora29 directory contents:

repodata
xorg-x11-drv-ati-7.9.0-3.fc27.x86_64.rpm
xorg-x11-drv-dummy-0.3.7-5.fc27.x86_64.rpm
xorg-x11-drv-evdev-2.10.5-4.fc27.x86_64.rpm
xorg-x11-drv-fbdev-0.4.3-28.fc27.x86_64.rpm
xorg-x11-drv-intel-2.99.917-30.20160929.fc27.x86_64.rpm
xorg-x11-drv-libinput-0.26.0-1.fc27.x86_64.rpm
xorg-x11-drv-nouveau-1.0.15-3.fc27.x86_64.rpm
xorg-x11-drv-qxl-0.1.5-5.fc27.x86_64.rpm
xorg-x11-drv-v4l-0.2.0-50.fc27.x86_64.rpm
xorg-x11-drv-vesa-2.3.2-28.fc27.x86_64.rpm
xorg-x11-drv-vmware-13.2.1-4.fc27.x86_64.rpm
xorg-x11-drv-wacom-0.35.0-3.fc27.x86_64.rpm
xorg-x11-server-common-1.19.6-7.fc27.x86_64.rpm
xorg-x11-server-Xorg-1.19.6-7.fc27.x86_64.rpm


kernel-4.18.16-300.fc29.x86_64.rpm
kernel-core-4.18.16-300.fc29.x86_64.rpm
kernel-cross-headers-4.18.16-300.fc29.x86_64.rpm
kernel-devel-4.18.16-300.fc29.x86_64.rpm
kernel-headers-4.18.16-300.fc29.x86_64.rpm
kernel-modules-4.18.16-300.fc29.x86_64.rpm
kernel-modules-extra-4.18.16-300.fc29.x86_64.rpm
kernel-tools-4.18.10-300.fc29.x86_64.rpm
kernel-tools-libs-4.18.10-300.fc29.x86_64.rpm
kernel-tools-libs-devel-4.18.10-300.fc29.x86_64.rpm
repodata

An appendix, because of text volume, showing the .ks file changes, is in
the post submission following this one.

Len E.

Part2 required because of text volume.

The following 2 excerpts are from the start and end portions of the .ks file, to
illustrate the only differences from previous kickstarts.



# Generated by pykickstart v3.32
#version=DEVEL
# X Window System configuration information
xconfig --startxonboot
# Keyboard layouts
keyboard 'us'
# Root password
rootpw --iscrypted --lock locked
# System language
lang en_US.UTF-8
# Shutdown after installation
shutdown
# Network information
network --bootproto=dhcp --device=link --activate
# Firewall configuration
firewall --enabled --service=mdns
# Use network installation
url --url https://download.rockylinux.org/stg/rocky/8/BaseOS/$basearch/os/
repo --name="BaseOS" --baseurl=http://dl.rockylinux.org/pub/rocky/8/BaseOS/$basearch/os/ --excludepkgs=kernel-cross-he
aders --cost=200
repo --name="AppStream" --baseurl=http://dl.rockylinux.org/pub/rocky/8/AppStream/$basearch/os/ --excludepkgs=xorg-x11-
drv*,xorg-x11-server-Xorg,xorg-x11-server-common --cost=200 
repo --name="PowerTools" --baseurl=http://dl.rockylinux.org/pub/rocky/8/PowerTools/$basearch/os/ --excludepkgs=kernel-
tools-libs-devel --cost=200
repo --name="extras" --baseurl=http://dl.rockylinux.org/pub/rocky/8/extras/$basearch/os --cost=200
repo --name="epel" --baseurl=https://dl.fedoraproject.org/pub/epel/8/Everything/$basearch/ --cost=200
repo --name="epel-modular" --baseurl=https://dl.fedoraproject.org/pub/epel/8/Modular/$basearch/ --cost=200


# elrepo repository - required for kmods
repo --name="elrepo" --baseurl=https://elrepo.org/linux/elrepo/el8/$basearch/ --cost=200


# Fedora29-local repository - provides fc29 kernel packages
repo --name="Fedora29" --baseurl=file:///var/lib/rpm/Fedora29/ --cost=200


# Fedora27-local repository - provides fc27 graphics packages
repo --name="Fedora27" --baseurl=file:///var/lib/rpm/Fedora27/ --cost=200


# System timezone

Excerpt # 2



%packages
@anaconda-tools
@base-x
@core
@dial-up
@fonts
@guest-desktop-agents
@hardware-support
@input-methods
@multimedia
@standard
@xfce-desktop
aajohan-comfortaa-fonts
anaconda
anaconda-install-env-deps
anaconda-live
# xfburn not available; use brasero instead
brasero
#
chkconfig
dracut-live
epel-release
f32-backgrounds-extras-xfce
f32-backgrounds-xfce
# fedora 29 and 27 gpg keys
# 
# fedora-gpg-keys
#
#
firefox
firewall-config
geany
glibc-all-langpacks
gparted
# 2 additional packages to base-x
initial-setup-gui
spice-vdagent
# 
initscripts
kernel
kernel-modules
kernel-modules-extra
# explicitly include optional packages
kernel-devel
kernel-cross-headers
#
memtest86+
mousepad
pavucontrol
pcp-selinux
pidgin
rhythmbox
ristretto
rocky-backgrounds
lightdm
seahorse
syslinux
thunderbird
transmission
wget
xfce4-about
xfce4-appfinder
xfce4-battery-plugin
xfce4-datetime-plugin
xfce4-netload-plugin
xfce4-places-plugin
xfce4-pulseaudio-plugin
xfce4-screenshooter-plugin
xfce4-smartbookmark-plugin
xfce4-systemload-plugin
xfce4-taskmanager
xfce4-time-out-plugin
xfce4-weather-plugin
xfce4-whiskermenu-plugin
xfdashboard
xfdashboard-themes
xdg-user-dirs
xdg-user-dirs-gtk
-acpid
-aspell-*
-autofs
-desktop-backgrounds-basic
-gdm
-gimp-help
-gnome-menus
-gnome-shell
-hplip
-isdn4k-utils
-mpage
-sane-backends
-xfce4-eyes-plugin
-xfce4-sensors-plugin
-xsane
-xsane-gimp


# elrepo packages
elrepo-release
kmod-sata_nv
kmod-forcedeth




%end


%post


yum install -y file:///var/lib/rpm/Fedora29/kernel*.rpm
yum install -y file:///var/lib/rpm/Fedora27/xorg-x11-*.rpm


%end

Len E.

Hi Nazunalika:

Some further progress in testing on my HP DC5800 machine since my submission
of Jan. 18 about it. On Jan. 19, I had taken one more step with it. From
Build System Info | koji, I downloaded the build.log for the
mock-5.3-1.el8 package with a finish date of 2023-12-13. In searching
the log file with pluma, I found absolutely no reference to libfc or fcoe.

Accordingly, I downloaded the mock-5.3-1.el8 package, and downgraded
mock to it on the HP DC5800. I ran the mock test using your standard
command sequence, the only variation being the insertion of nano, libguestfs-xfs
and xfsprogs in front of lorax-lmc-novirt on the mock --install command.
The run failed, not because of libfc or xfs warnings, but with the same
fedora29-media repodata error being experienced on my HP Pavilion Media
Centre HPm8247c. I then deferred any more effort on the DC5800 and
resumed testing on the HPm8247c.


With the success achieved on the HPm8247c as reported in my previous
submission, I ran the same test with the same steps and materials on the DC5800,
the only difference being the mock --install command described above.

The mock run succeeded. As with the HPm8247c outcome, I burned a DVD
of the .iso with k3b and installed it on my Compaq Presario machine and checked
to ensure that it was complete and functioning properly.


It remains a mystery to me why the libfc and xfs problem occurred on the
DC5800 and was not a factor on the HPm8247c. It’s just something to be
aware of in future work.


I am closing this post off now.
Thank you for your support !

Len E.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.