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
I am experiencing an issue with rpm-ostree while trying to manually update the system. Currently, I have configured my zincati to perform updates automatically on weekends. However, when I check for updates with rpm-ostree, it notifies me that there is an update pending:
Ideally, I should be able to update the system manually regardless of the zincati update strategy. However, this is not happening. The only way I can trigger a manual update is by disabling the zincati configuration by renaming it:
Following this, I receive a broadcast message notifying me that an update is about to take place:
Broadcast message from Zincati at Thu 2023-07-27 14:07:36 UTC:
New update 38.20230709.3.0 is available and has been deployed.
If permitted by the update strategy, Zincati will reboot into this update when
all interactive users have logged out, or in 10 minutes, whichever comes
earlier. Please log out of all active sessions in order to let the auto-update
process continue.
This behavior is unexpected. I guess I should be able to update the system at any time without having to alter the zincati configuration.
The text was updated successfully, but these errors were encountered:
kavishgr
changed the title
Unable to Manually Update System with rpm-ostree when zincati Configuration is Active
Unable to trigger a manual ppdate with rpm-ostree when zincati update strategy is active
Jul 27, 2023
kavishgr
changed the title
Unable to trigger a manual ppdate with rpm-ostree when zincati update strategy is active
Unable to trigger a manual update with rpm-ostree when a zincati update strategy is active
Jul 27, 2023
Yes, this is extremely confusing. I generally agree with you, however there's a high degree of subtlety and complexity in the interaction between the two components today, and "user control" becomes a major third one.
I am experiencing an issue with rpm-ostree while trying to manually update the system. Currently, I have configured my zincati to perform updates automatically on weekends. However, when I check for updates with rpm-ostree, it notifies me that there is an update pending:
but attempting to upgrade results in a message stating that no upgrade is available:
This is my update strategy:
Ideally, I should be able to update the system manually regardless of the zincati update strategy. However, this is not happening. The only way I can trigger a manual update is by disabling the zincati configuration by renaming it:
and restarting the zincati service:
When I check with the
rpm-ostree status -v
command, the state shows as busy, indicating that it is about to update to a new deployment:Following this, I receive a broadcast message notifying me that an update is about to take place:
This behavior is unexpected. I guess I should be able to update the system at any time without having to alter the zincati configuration.
The text was updated successfully, but these errors were encountered: