CoreOS version on stable release channel reverted back from 1068.6.0 to 1010.6 ?

[Umesh Tyagi]

As part of our build pipeline we run tests against CoreOS stable release channel and make sure our product remains compatible with the new OS versions. 

So Yesterday ( 07/15/2016) update against stable release channel installed version 1068.6.0 on our test VMs however,  today (07/16/2016)  it is downloading 1010.6 ?

https://coreos.com/releases/ still shows 1068.6.0 as the current stable release. 

Not sure if it is an explicit revert back by CoreOS or a bug ? I am not able to find any announcement regarding the revert back on CoreOS website. 

The whole idea of using stable release channel to have some stability is getting lost in this back and forth switching of OS versions . It is completely throwing off our build pipeline because of certain changes between the two versions.

Thanks,

Umesh

[Alex Crawford]

On 07/15, Umesh Tyagi wrote:
> So Yesterday ( 07/15/2016) update against stable release channel installed
> version 1068.6.0 on our test VMs however, today (07/16/2016) it is
> downloading 1010.6 ?

The public updates have been slowed due to a systemd regression. We will
continue the rollout once it has been patched.

> https://coreos.com/releases/ still shows 1068.6.0 as the current stable
> release.
>
> Not sure if it is an explicit revert back by CoreOS or a bug ? I am not
> able to find any announcement regarding the revert back on CoreOS website.

The current Stable is still 1068.6.0 - the site and asset buckets are
accurate. We are just not actively pushing it out.

> The whole idea of using stable release channel to have some stability is
> getting lost in this back and forth switching of OS versions . It is
> completely throwing off our build pipeline because of certain changes
> between the two versions.

There is a difference between making images available for download and
actively pushing images to machines. We are much more cautious when it
comes to actively updating machines, so you'll notice from time to time
that it lags. If you want more control over the updates that are offered
to your deployment, you can use CoreUpdate [1]. This is the same
software that we use internally to serve updates globally.

For what it's worth, relying on the public updates for homogeneity is
not going to end well. The update server rate limits the updates it
serves - it is not guaranteed that two machines who request an update
will both get it. If you need homogeneity, you will need to use
CoreUpdate or explicitly install specific versions of CoreOS.

I hope that helps.

-Alex

[1]: https://coreos.com/products/premium-managed-linux