Closed ureiihtur closed 9 months ago
Do you have ssh access on the nodes? Check if rpm-ostreed.service
is running and rpm-ostree status
doesn't have pending deployments
Do you have ssh access on the nodes? Check if
rpm-ostreed.service
is running andrpm-ostree status
doesn't have pending deployments
The rpm-ostreed had dependency fail from all of the cluster nodes
rpm-ostree status
A dependency job for rpm-ostreed.service failed. See 'journalctl -xe' for details.
○ rpm-ostreed.service - rpm-ostree System Management Daemon
Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed.service; static)
Drop-In: /etc/systemd/system/rpm-ostreed.service.d
└─10-mco-default-env.conf
/usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
/run/systemd/system/rpm-ostreed.service.d
└─bug2111817.conf
/etc/systemd/system/rpm-ostreed.service.d
└─mco-controlplane-nice.conf
Active: inactive (dead)
Docs: man:rpm-ostree(1)
Jan 23 09:43:34 master2.test.yaude.com systemd[1]: Dependency failed for rpm-ostreed.service - rpm-ostree System Management Daemon.
Jan 23 09:43:34 master2.test.yaude.com systemd[1]: rpm-ostreed.service: Job rpm-ostreed.service/start failed with result 'dependency'.
Jan 23 09:48:45 master2.test.yaude.com systemd[1]: Dependency failed for rpm-ostreed.service - rpm-ostree System Management Daemon.
Jan 23 09:48:45 master2.test.yaude.com systemd[1]: rpm-ostreed.service: Job rpm-ostreed.service/start failed with result 'dependency'.
Jan 23 09:53:48 master2.test.yaude.com systemd[1]: Dependency failed for rpm-ostreed.service - rpm-ostree System Management Daemon.
Jan 23 09:53:48 master2.test.yaude.com systemd[1]: rpm-ostreed.service: Job rpm-ostreed.service/start failed with result 'dependency'.
Jan 23 09:59:00 master2.test.yaude.com systemd[1]: Dependency failed for rpm-ostreed.service - rpm-ostree System Management Daemon.
Jan 23 09:59:00 master2.test.yaude.com systemd[1]: rpm-ostreed.service: Job rpm-ostreed.service/start failed with result 'dependency'.
Jan 23 10:01:30 master2.test.yaude.com systemd[1]: Dependency failed for rpm-ostreed.service - rpm-ostree System Management Daemon.
Jan 23 10:01:30 master2.test.yaude.com systemd[1]: rpm-ostreed.service: Job rpm-ostreed.service/start failed with result 'dependency'.
error: Loading sysroot: exit status: 1
That's odd, its only dependency is mounted /boot
. Check that all mounts have succeeded?
That's odd, its only dependency is mounted
/boot
. Check that all mounts have succeeded?
It seems like failed mount, can found messages from systemd
Jan 23 07:27:40 localhost systemd[1]: Dependency failed for boot.mount - CoreOS Dynamic Mount for /boot.
Jan 23 07:27:40 localhost systemd[1]: Dependency failed for boot.mount - CoreOS Dynamic Mount for /boot.
Jan 23 09:03:05 bootstrap.test.yaude.com systemd[1]: Dependency failed for boot.mount - CoreOS Dynamic Mount for /boot.
Jan 23 09:03:54 bootstrap.test.yaude.com systemd[1]: Dependency failed for boot.mount - CoreOS Dynamic Mount for /boot.
Jan 23 10:00:59 bootstrap.test.yaude.com systemd[1]: Dependency failed for boot.mount - CoreOS Dynamic Mount for /boot.
Jan 23 10:13:30 bootstrap.test.yaude.com systemd[1]: Dependency failed for boot.mount - CoreOS Dynamic Mount for /boot.
And there is alwasy a message when SSH login, do they relate to each other?
Fedora CoreOS 38.20231027.3.2
############################################################################
WARNING: This system has layered modularity RPMs. In Fedora 39 modularity
has been retired. The system will most likely stop updating successfully
when Fedora CoreOS transitions to Fedora 39. See this tracker for more info:
https://github.com/coreos/fedora-coreos-tracker/issues/1513
To disable this warning, use:
sudo systemctl disable coreos-check-modularity.service
############################################################################
I have also encountered this problem. How did you solve it?
I replaced Fedora 39 with 38, the problem is solved.
我用 Fedora 39 替换了 Fedora 38,问题解决了。
I have successfully solved this problem according to your method. Thank you very much for your help
Describe the bug
The oc command can get a machine-config error
And getting further information, found an osImageURL error in daemon container.
Version 4.14.0-0.okd-2024-01-06-084517 UPI
How reproducible 100% of the time
Log bundle Log bundle