Closed pizzarabe closed 5 years ago
According to @robszumski there is a rate limit if you are downloading newer images with update_check_scheduler. I guess we should add this to the documentation. And I would love to know what this rate_limit is.
@pizzarabe Where do you think it makes sense to add this documentation? My worry is that it is a bit complicated to explain, as the rate limit can change based on certain factors, etc.
The Documentation already mention the rate limit but without a explanation:
[...]you can force an update check, which will skip any rate-limiting settings that are configured in CoreUpdate.
Maybe we can add the explanation on this page (or link there to the explanation page)?
As a sysadmin, trying to build a coreos infrastructure with the information provided from the docs, this is a nontransparent behavior (I thought I had a mistake in my cloud-config file).
Like i said, i don't know about the rate_limit, but if this feature is difficult to explain, we should definitive document it because understanding this feature without any documentation is even more difficult :) .
Should probably just leave a link to CoreUpdate. Basically, users should not depend on the scheduling of updates from the public update servers. The public update servers are catering to the global population of CoreOS Linux instances, which is generally more conservative than any one user/deployment. If more control over updates is needed, it's necessary to run your own update service.
Thank you for reporting this issue. Unfortunately, we don't think we'll end up addressing it in Container Linux.
We're now working on Fedora CoreOS, the successor to Container Linux, and we expect most major development to occur there instead. Meanwhile, Container Linux will be fully maintained into 2020 but won't see many new features. We appreciate your taking the time to report this issue and we're sorry that we won't be able to address it.
My CoreOS 1068.9.0 is unable to find a newer version of CoreOS if he is using the update_check_scheduler.
If I start the update manually with
update_engine_client -check_for_update
the updater is able to find a newer version and is updating like expected.The used cloud-init was:
Environment
ISO installation.
Expected Behavior
The Update_Engine should find a newer version, if available
Environment
VMWare