This repository was archived by the owner on Jan 16, 2024. It is now read-only.
one-context-force.service fails on ubuntu 18.04 #118
Labels
Milestone
Comments
|
There are several systemd services to deal with different situations, but the main ones you should check are Please check the status of Thank you. |
|
Also, also check this issue #119 (comment) just in case you didn't do clean package installation, but just upgraded already installed older package. |
|
Hi Do we have a "work around" for this ? We have this issue with the 5.8.0 release on ubuntu 18.04, the services
and
are both active `● one-context.service - OpenNebula contextualization script mars 01 15:16:15 eolebase-2.7.0 systemd[1]: Starting OpenNebula contextualization script... mars 01 15:14:14 eolebase-2.7.0 one-contextd[1035]: Script loc-14-mount-swap: Finished with exit code 255 |
|
I have the same issue on Debian Buster. It looks like the I added a some debug in the script to see what's happening: --- /usr/sbin/one-context-run.orig 2019-07-09 16:15:12.807287544 +0200
+++ /usr/sbin/one-context-run 2019-07-09 16:15:19.831274161 +0200
@@ -36,5 +36,6 @@
fi
else
echo 'Contextualization must start first as a boot service' >&2
+ ls -l $(dirname ${CONTEXT_BASE}) >&2
exit 1
fiLooking at the last boot logs I see that Seems that there is an issue with systemd ordering. |
|
I don't undestand how a disabled service can be started by It's not even referenced in list-dependencies: Am I missing something? |
|
Ok, the problem may be due to |
baby-gnu
added a commit
to eole/addon-context-linux
that referenced
this issue
Jul 11, 2019
We must make sure "one-context-force.service" is not run during boot disk detection but on hotplug events. When booting with a swap partition on the disk, the udev rules will start the "one-context-force" service long before "one-context-local" and "one-context". This results in the system being in "degraded" state as reported by "systemctl is-system-running". * src/usr/lib/systemd/system/one-context-force.service##systemd.one: add conditions to run only on hotplug events.
baby-gnu
added a commit
to eole/addon-context-linux
that referenced
this issue
Jul 11, 2019
We must make sure "one-context-force.service" is not run during boot disk detection but on hotplug events. When booting with a swap partition on the disk, the udev rules will start the "one-context-force" service long before "one-context-local" and "one-context". This results in the system being in "degraded" state as reported by "systemctl is-system-running". * src/usr/lib/systemd/system/one-context-force.service##systemd.one: add conditions to run only on hotplug events. Signed-off-by: Daniel Dehennin <[email protected]>
baby-gnu
added a commit
to eole/addon-context-linux
that referenced
this issue
Jul 11, 2019
We must make sure "one-context-force.service" is not run during boot disk detection but on hotplug events. When booting with a swap partition on the disk, the udev rules will start the "one-context-force" service long before "one-context-local" and "one-context". This results in the system being in "degraded" state as reported by "systemctl is-system-running". * src/usr/lib/systemd/system/one-context-force.service##systemd.one: add conditions to run only on hotplug events. Signed-off-by: Daniel Dehennin <[email protected]>
vholer
pushed a commit
that referenced
this issue
Aug 14, 2019
We must make sure "one-context-force.service" is not run during boot disk detection but on hotplug events. When booting with a swap partition on the disk, the udev rules will start the "one-context-force" service long before "one-context-local" and "one-context". This results in the system being in "degraded" state as reported by "systemctl is-system-running". * src/usr/lib/systemd/system/one-context-force.service##systemd.one: add conditions to run only on hotplug events. Signed-off-by: Daniel Dehennin <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I installed an ubuntu18.04 server image with the one-context_5.6.0-1.deb package. My context section is just
and I get the above error on boot.
The text was updated successfully, but these errors were encountered: