-
Notifications
You must be signed in to change notification settings - Fork 305
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question: ostree admin upgrade does it twice #640
Comments
You can do the "download but don't deploy" with a raw "ostree pull". We don't have good porcelain for this right now though. |
One would expect
|
Yes - it's complex, one reason we do a redeploy is to re-do copying /etc, in case there were any changes. See also coreos/rpm-ostree#40 Big picture, at some point I'd like to merge the "pure ostree daemon" code from https://github.com/endlessm/eos-updater into ostree, and have it support things like "background pull of updates, deploy last pulled and reboot". |
Daemon aside, I think it'd be pretty easy to implement:
|
We use it in a desktop environment and we want to prevent a reboot (users can be working on their desktop and do not appreciate a reboot in the middle of their work). Will have a look at https://github.com/endlessm/eos-updater |
This makes it easier to script downloading updates in the background, and only do deployments just before rebooting. Partially addresses ostreedev#640
I took a quick crack at this in #642 |
This makes it easier to script downloading updates in the background, and only do deployments just before rebooting. Partially addresses ostreedev#640
This makes it easier to script downloading updates in the background, and only do deployments just before rebooting. Partially addresses ostreedev#640
Going to close this as fixed by #642 - but I only lightly tested that, so feel free to reopen. There's definitely bigger picture stuff here around having better tooling than raw |
When we run a ostree admin upgrade it deploys a new one (when there is one).
When you run it again (and you did not reboot yet to the new one) it does a redeploy of the already deployed again.
Why does it redeploy when the last one was successful?
We want to cron the upgrade task on the desktops but we are limited to daily because we do not want to reboot automatically but we want to check for updates more frequently.
The text was updated successfully, but these errors were encountered: