update-engine says no updates for CoreOS 1068.10.0

60 views
Skip to first unread message

Gin

unread,
Mar 28, 2018, 12:29:46 PM3/28/18
to CoreOS User
Hi,

I am using CoreOS images to spin off servers on Rackspace Public Cloud.
Every time I create a new instance I have to update the OS because Rackspace provides an outdated CoreOS image - 1068.10.0, Release Date: August 23, 2016.

Something happened today and I can no longer update an outdated Rackspace CoreOS image(1068.10.0, Release Date: August 23, 2016).
I understand that Rackspace no longer updates their CoreOS images (or vice versa - CoreOS no longer supports Rackspace). 
However, the updates were working just fine up until yesterday. Hence the question.

Any pointers would be welcome. 

Here is a code snippet from the update-engine process:
update_engine[677]: [0328/154313:INFO:dbus_service.cc(57)] Attempting interactive update
update_engine
[677]: [0328/154313:INFO:update_attempter.cc(256)] New update check requested
update_engine
[677]: [0328/154313:INFO:omaha_request_params.cc(60)] Current group set to stable
update_engine
[677]: [0328/154313:INFO:update_attempter.cc(475)] Already updated boot flags. Skipping.
update_engine
[677]: [0328/154313:INFO:update_attempter.cc(658)] Scheduling an action processor start.
update_engine
[677]: [0328/154313:INFO:action_processor.cc(36)] ActionProcessor::StartProcessing: OmahaRequestAction
update_engine
[677]: [0328/154313:INFO:omaha_request_action.cc(257)] Posting an Omaha request to https://public.update.core-os.net/v1/update/
update_engine
[677]: [0328/154313:INFO:omaha_request_action.cc(258)] Request: <?xml version="1.0" encoding="UTF-8"?>
update_engine
[677]: <request protocol="3.0" version="CoreOSUpdateEngine-0.1.0.0" updaterversion="CoreOSUpdateEngine-0.1.0.0" installsource="ondemandupdate" ismachine="1">
update_engine
[677]: <os version="Chateau" platform="CoreOS" sp="1068.10.0_x86_64"></os>
update_engine
[677]: <app appid="{e96281a6-d1af-4bde-9a0a-97b76e56dc57}" version="1068.10.0" track="stable" bootid="{39f5433a-fb2d-4ec3-9b11-e4edd4583124}" oem="rackspace" oemversion="0.0.4" alephversion="1068.10.0" machineid="f42a0d273ab548adab3230e4cff60655" lang="en-US" board="amd64-usr" hardware_class="" delta_okay="false" >
update_engine
[677]: <ping active="1"></ping>
update_engine
[677]: <updatecheck></updatecheck>
update_engine[677]: <event eventtype="3" eventresult="2" previousversion=""></
event>
update_engine
[677]: </app>
update_engine[677]: </
request>
update_engine
[677]: [0328/154313:INFO:libcurl_http_fetcher.cc(48)] Starting/Resuming transfer
update_engine
[677]: [0328/154313:INFO:libcurl_http_fetcher.cc(164)] Setting up curl options for HTTPS
update_engine
[677]: [0328/154313:INFO:libcurl_http_fetcher.cc(427)] Setting up timeout source: 1 seconds.
update_engine
[677]: [0328/154313:INFO:libcurl_http_fetcher.cc(240)] HTTP response code: 200
update_engine
[677]: [0328/154313:INFO:libcurl_http_fetcher.cc(297)] Transfer completed (200), 267 bytes downloaded
update_engine
[677]: [0328/154313:INFO:omaha_request_action.cc(574)] Omaha request response: <?xml version="1.0" encoding="UTF-8"?>
update_engine
[677]: <response protocol="3.0" server="update.core-os.net">
update_engine
[677]: <daystart elapsed_seconds="0"></daystart>
update_engine
[677]: <app appid="e96281a6-d1af-4bde-9a0a-97b76e56dc57" status="ok">
update_engine
[677]: <updatecheck status="noupdate"></updatecheck>
update_engine
[677]: </app>
update_engine[677]: </
response>
update_engine
[677]: [0328/154313:INFO:omaha_request_action.cc(394)] No update.
update_engine
[677]: [0328/154313:INFO:action_processor.cc(82)] ActionProcessor::ActionComplete: finished OmahaRequestAction, starting OmahaResponseHandlerAction
update_engine
[677]: [0328/154313:INFO:omaha_response_handler_action.cc(36)] There are no updates. Aborting.
update_engine
[677]: [0328/154313:INFO:action_processor.cc(68)] ActionProcessor::ActionComplete: OmahaResponseHandlerAction action failed. Aborting processing.
update_engine
[677]: [0328/154313:INFO:action_processor.cc(73)] ActionProcessor::ActionComplete: finished last action of type OmahaResponseHandlerAction
update_engine
[677]: [0328/154313:INFO:update_attempter.cc(283)] Processing Done.
update_engine
[677]: [0328/154313:INFO:update_attempter.cc(319)] No update

Cheers,
Gintas

Stephen Lowrie

unread,
Mar 28, 2018, 12:33:07 PM3/28/18
to Gin, CoreOS User
Gintas,

All stable updates are currently paused, more information available @ https://github.com/coreos/bugs/issues/2391#issuecomment-376905983

Thanks,
--Stephen

--
You received this message because you are subscribed to the Google Groups "CoreOS User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to coreos-user+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gintautas Sulskus

unread,
Mar 28, 2018, 12:35:17 PM3/28/18
to Stephen Lowrie, CoreOS User
Thanks!


update_engine
[677]: [0328/154313:INFO:action_processor.cc(82)] ActionProcessor::ActionComplete: finished OmahaRequestAction,starting OmahaResponseHandlerAction

update_engine
[677]: [0328/154313:INFO:omaha_response_handler_action.cc(36)] There are no updates. Aborting.

update_engine
[677]: [0328/154313:INFO:action_processor.cc(68)] ActionProcessor::ActionComplete: OmahaResponseHandlerActionaction failed. Aborting processing.

update_engine
[677]: [0328/154313:INFO:action_processor.cc(73)] ActionProcessor::ActionComplete: finished last action of type OmahaResponseHandlerAction
update_engine
[677]: [0328/154313:INFO:update_attempter.cc(283)] Processing Done.
update_engine
[677]: [0328/154313:INFO:update_attempter.cc(319)] No update

Cheers,
Gintas

Stephen Lowrie

unread,
Mar 29, 2018, 10:25:49 PM3/29/18
to Gintautas Sulskus, CoreOS User
Stable updates are now unpaused, more information @ https://groups.google.com/d/msg/coreos-user/5ihE2cKuYck/G-J7D-r-AwAJ

--Stephen

On Wed, Mar 28, 2018 at 9:34 AM, Gintautas Sulskus <gintauta...@gmail.com> wrote:
Thanks!

On 28 Mar 2018, at 17:33, Stephen Lowrie <stephen...@coreos.com> wrote:

Gintas,

All stable updates are currently paused, more information available @ https://github.com/coreos/bugs/issues/2391#issuecomment-376905983

Thanks,
--Stephen
Reply all
Reply to author
Forward
0 new messages