7ieylw
Last Updated: April 18, 2016
·
1.373K
· superboum
Avatar1

Unable to udapte CoreOS

You might have a single CoreOS instance and try to update it manually but fail with this message :

quentin@glados /srv/glados $ update_engine_client -check_for_update
[0418/130944:INFO:update_engine_client.cc(243)] Initiating update check and install.
[0418/130944:WARNING:update_engine_client.cc(59)] Error getting dbus proxy for com.coreos.update1: GError(3): Could not get owner of name 'com.coreos.update1': no such name
[0418/130944:INFO:update_engine_client.cc(50)] Retrying to get dbus proxy. Try 2/4
[0418/130954:WARNING:update_engine_client.cc(59)] Error getting dbus proxy for com.coreos.update1: GError(3): Could not get owner of name 'com.coreos.update1': no such name
[0418/130954:INFO:update_engine_client.cc(50)] Retrying to get dbus proxy. Try 3/4
[0418/131004:WARNING:update_engine_client.cc(59)] Error getting dbus proxy for com.coreos.update1: GError(3): Could not get owner of name 'com.coreos.update1': no such name
[0418/131004:INFO:update_engine_client.cc(50)] Retrying to get dbus proxy. Try 4/4
[0418/131014:WARNING:update_engine_client.cc(59)] Error getting dbus proxy for com.coreos.update1: GError(3): Could not get owner of name 'com.coreos.update1': no such name
[0418/131014:ERROR:update_engine_client.cc(64)] Giving up -- unable to get dbus proxy for com.coreos.update1

That's probably because you have deactivated the update engine in one of your cloud config (don't know if it comes from reboot strategy or not). So unmask and start the systemd service :

sudo systemctl unmask update-engine.service
sudo systemctl start update-engine.service

Now you can try a manual check :

update_engine_client -check_for_update

You can follow the update progression with this command :
sudo journalctl -fu update-engine

Source: https://botbot.me/freenode/coreos/2015-03-30/?page=9

Say Thanks
Respond
Filed Under