Description of problem: Sometimes, mock on F34 fails with "Failed to register machine: The name is not activatable" error when we build an SRPM in our CI. Version-Release number of selected component (if applicable): mock-2.9-2.fc34 How reproducible: Sometimes, doesn't happen everytime Logs: $ sudo mock -r "$fedora-34-x86_64" --buildsrpm \ --define "commit ce1339d29c0232502e2f2f44986cc5bc701e00c1" \ --spec ./osbuild-composer.spec \ --sources "./osbuild-composer-ce1339d29c0232502e2f2f44986cc5bc701e00c1.tar.gz" \ --resultdir ./srpm [2021-02-22T12:40:08.704Z] INFO: mock.py version 2.9 starting (python version = 3.9.1, NVR = mock-2.9-2.fc34)... [2021-02-22T12:40:08.704Z] Start(bootstrap): init plugins [2021-02-22T12:40:08.704Z] INFO: selinux enabled [2021-02-22T12:40:08.704Z] Finish(bootstrap): init plugins [2021-02-22T12:40:08.704Z] Start: init plugins [2021-02-22T12:40:08.704Z] INFO: selinux enabled [2021-02-22T12:40:08.704Z] Finish: init plugins [2021-02-22T12:40:09.109Z] INFO: Signal handler active [2021-02-22T12:40:09.109Z] Start: run [2021-02-22T12:40:09.109Z] INFO: Start(./osbuild-composer.spec) Config(fedora-34-x86_64) [2021-02-22T12:40:09.109Z] Start: clean chroot [2021-02-22T12:40:09.109Z] Finish: clean chroot [2021-02-22T12:40:09.109Z] Start(bootstrap): chroot init [2021-02-22T12:40:09.109Z] INFO: calling preinit hooks [2021-02-22T12:40:09.109Z] INFO: enabled root cache [2021-02-22T12:40:09.109Z] INFO: enabled package manager cache [2021-02-22T12:40:09.109Z] Start(bootstrap): cleaning package manager metadata [2021-02-22T12:40:09.109Z] Finish(bootstrap): cleaning package manager metadata [2021-02-22T12:40:09.109Z] INFO: enabled HW Info plugin [2021-02-22T12:40:09.109Z] Mock Version: 2.9 [2021-02-22T12:40:09.109Z] INFO: Mock Version: 2.9 [2021-02-22T12:40:09.523Z] Finish(bootstrap): chroot init [2021-02-22T12:40:09.523Z] Start: chroot init [2021-02-22T12:40:09.523Z] INFO: calling preinit hooks [2021-02-22T12:40:09.523Z] INFO: enabled root cache [2021-02-22T12:40:09.523Z] INFO: enabled package manager cache [2021-02-22T12:40:09.523Z] Start: cleaning package manager metadata [2021-02-22T12:40:09.523Z] Finish: cleaning package manager metadata [2021-02-22T12:40:09.523Z] INFO: enabled HW Info plugin [2021-02-22T12:40:09.930Z] Mock Version: 2.9 [2021-02-22T12:40:09.930Z] INFO: Mock Version: 2.9 [2021-02-22T12:40:09.930Z] Start: dnf install [2021-02-22T12:40:10.805Z] ERROR: Exception(./osbuild-composer.spec) Config(fedora-34-x86_64) 0 minutes 1 seconds [2021-02-22T12:40:10.805Z] INFO: Results and/or logs in: ./srpm [2021-02-22T12:40:10.805Z] INFO: Cleaning up build root ('cleanup_on_failure=True') [2021-02-22T12:40:10.805Z] Start: clean chroot [2021-02-22T12:40:10.805Z] Finish: clean chroot [2021-02-22T12:40:10.805Z] ERROR: Command failed: [2021-02-22T12:40:10.805Z] # /usr/bin/systemd-nspawn -q -M a847ccfd8ec64ca09893127dbe31962b -D /var/lib/mock/fedora-34-x86_64-bootstrap/root -a --capability=cap_ipc_lock --bind=/tmp/mock-resolv.7kpdq3zp:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-34-x86_64/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007" --setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=C.UTF-8 --setenv=LC_MESSAGES=C.UTF-8 --resolv-conf=off /usr/bin/dnf --installroot /var/lib/mock/fedora-34-x86_64/root/ --releasever 34 --setopt=deltarpm=False --allowerasing --disableplugin=local --disableplugin=spacewalk install @buildsys-build --setopt=tsflags=nocontexts [2021-02-22T12:40:10.805Z] Failed to register machine: The name is not activatable
I'm not sure what makes the machine "non activatable", so I'm switching against systemd-nspawn (this is not reproducible on our boxes). For the test blocker issue, work-around is to use `--isolation=simple` option.
This might be an issue with `dbus-broker-26-1`, which was installed on this system. `dbus-broker-27-2` fixes some related issues. @Ondrej can you confirm whether this fixes the issue?
Crosslinking https://pagure.io/fedora-ci/general/issue/217
This issue appeared once again, this time with dbus-broker-27-2.fc34
Is it possible to get more information on this? Does the journal show anything? Is `systemctl status systemd-machined` showing anything of interest? Is `systemd-machined` listed in `busctl` as `activatable` when this bug happens?
Let's reassign this to dbus-broker for now. Nothing has changed in the way systemd-machined is declared in a long time, and if the the issue comes and goes, then it seems more likely that it's something on the broker side.
I am closing this, since there has not been any follow-up. Without any system-log or other input it is hard to judge what is going wrong. I will gladly investigate if this pops up again.
On a related note, I now see the very same error on the c9s Zuul CI :(