stefhen
May 13, 2020, 9:34pm
1
Hi,
I move from CoreOS to Fedora CoreOS and I would like to know how I can disable auto-update on FCOS, with the previous version it was as simple as:
thanks,
Steve
pauld
May 14, 2020, 1:09am
2
Fedora CoreOS… Do you means Silverblue?
According to:
updates are downloaded by default, but not done by default. And it is said:
this can be changed from the update preferences in Software
stefhen
May 14, 2020, 1:34am
3
No I mean Fedora CoreOS project Fedora CoreOS
The problem with autoupdate is the reboot, I don’t want my VM reboots anytime without my supervision.
Hi @stefhen ,
Fedora Core OS is a pretty special and recent thing, which has its own forum platform. If you don’t get the right answer here, I would suggest, asking there:
https://discussion.fedoraproject.org/c/server/coreos/
There is also an IRC channel and a mailing list that you could contact: Getting Started with Fedora CoreOS :: Fedora Docs
Update Streams :: Fedora Docs says that
sudo systemctl stop zincati.service
stops the service that performs the automatic updates…
If you don’t want to disable the service altogether, you can find a description on how to simply stop auto-updating here:
# Auto-updates
Available updates are discovered by periodically polling a [Cincinnati] server.
Once available, they are automatically applied via [rpm-ostree] and a machine reboot.
[Cincinnati]: https://github.com/openshift/cincinnati
[rpm-ostree]: https://github.com/projectatomic/rpm-ostree
## Phased rollouts, client wariness, canaries
Once a new update payload is officially released, Zincati will eventually detect and apply the update automatically.
However, there is no strict guarantee on the timing for an individual node to detect a new release, as the server will try to spread updates over a controlled timeframe.
This mechanism is called "phased rollout" and is meant to help release engineers and administrators in performing gradual updates and catching last-minute issues before they propagate to a large number of machines.
Phased rollouts are orchestrated by the Cincinnati backend, by adjusting over time the percentage of clients to which an update is offered.
Clients do not usually need any additional setup to leverage phased rollouts.
By default, the Cincinnati backend dynamically assigns a specific rollout score to each client.
show original
stefhen
May 14, 2020, 1:51pm
6
thank you so much florian this fixes my problem
system
June 11, 2020, 1:55pm
7
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
