Update notification for the update of the podman machine image

[gbraad]

The podman machine image, which uses Fedora CoreOS, can automagically update. This needs a reboot to pivot to the new root.
We discussed this at some point that it might be user controlled or otherwise notified to the user.
This issue is to collect feedback around this.

[rhatdan]

Basically requires user to do
podman machine stop
podman machine start

[gbraad]

Usercontrolled => not wanting the update just yet as it might introduce unnecessary changes to the environment. Some corporate environments arent in favour of auto rollout or patching due to unforeseen consequences.

[afbjorklund]

Previously the VM would just auto-reboot after 10 mins, was this changed ?

• Add some documentation on how podman machine is updated #11680

[gbraad]

Good point. Honestly I don't know. I have been using CRC as you can imagine. But if so, that is actually a very 'bad' user experience as the user is not in control or has been provided feedback about this.

…

On Fri, Jun 10, 2022, 00:26 Anders Björklund ***@***.***> wrote: Previously the VM would just auto-reboot after 10 mins, was this changed ? — Reply to this email directly, view it on GitHub <#14514 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAOZR2YTUXWZVSPLLR3P3VOILK3ANCNFSM5YDMRJMQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[rhatdan]

@gbraad @afbjorklund Any update on this issue?

[afbjorklund]

No updates from me, as far as I know it will automatically reboot to receive the updates - and this is by (CoreOS) design

New update 35.20211029.2.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.

https://coreos.github.io/zincati/usage/updates-strategy/#immediate-strategy

By default, the immediate strategy is used in order to proactively keep machines up-to-date.

[core@localhost ~]$ uptime
 14:27:03 up 10 min,  1 user,  load average: 0.00, 0.01, 0.00
[core@localhost ~]$ Connection to localhost closed by remote host.
Connection to localhost closed.

[INFO zincati::update_agent::actor] target release '36.20220505.2.0' selected, proceeding to stage it

[Luap99]

@baude Do you think this is still relevant with the new machine image workflow?

[afbjorklund]

I think the new strategy was to disable the automatic updates

[Luap99]

I think the new strategy was to disable the automatic updates

I do not see how this is relevant for this issue. Even without auto updates we should still notify users that the VM can be updated, no?

[afbjorklund]

"The podman machine image, which uses Fedora CoreOS, can automagically update. "

If the zincati service is disabled, then the machine will not spontaneously reboot anymore?

94818f5