You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
Periodic recontextualization check for #185 doesn't happen on Debian-based systems which don't use systemd (e.g., Devuan), because there is a single .deb package for all Debian-like systems which contains only a systemd timer one-context-reconfigure.timer, but not a cron schedule (/etc/cron.d/one-context-reconfigure). Solution might be to
distribute both systemd timer and cron schedule in a single Debian pakage,
inside the cron-schedule, check and run only if timer is not active.
vholer
changed the title
Non-systemd based Debians don't recontextualize on vCenter
Non-systemd based Debians don't periodically recontextualize on vCenter
Oct 27, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Periodic recontextualization check for #185 doesn't happen on Debian-based systems which don't use systemd (e.g., Devuan), because there is a single
.deb
package for all Debian-like systems which contains only a systemd timerone-context-reconfigure.timer
, but not a cron schedule (/etc/cron.d/one-context-reconfigure
). Solution might be toRemove skip in tests when fixed: https://github.com/OpenNebula/development/blob/208bde38f0052c05d5eecc738509382b0ebff476/readiness/spec/context/linux/network.rb#L250
The text was updated successfully, but these errors were encountered: