Issue 666853 link

Starred by 1 user

Issue metadata

Status:	Archived
Owner:	----
Closed:	Nov 2016
Cc:	█ ntang@chromium.org █ pgeorgi@chromium.org pprabhu@chromium.org
Components:	Infra>Client>ChromeOS
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	2
Type:	Bug
current-issue VerifyIn-58 VerifyIn-59 VerifyIn-60 VerifyIn-61

wolf-tot-paladin failed in sanity test

Project Member Reported by skau@chromium.org, Nov 18 2016

Issue description

provision_AutoUpdate failed with RootfsUpdateError.

https://uberchromegw.corp.google.com/i/chromeos/builders/wolf-tot-paladin/builds/8380

11/18 09:23:38.333 INFO |        server_job:0153| START	86224982-chromeos-test/chromeos4-row1-rack7-host1/provision_AutoUpdate	provision	timestamp=1479488911	localtime=Nov 18 09:08:31	
11/18 09:23:38.333 INFO |        server_job:0153| 	FAIL	86224982-chromeos-test/chromeos4-row1-rack7-host1/provision_AutoUpdate	provision	timestamp=1479489720	localtime=Nov 18 09:22:00	Unhandled DevServerException: CrOS auto-update failed for host chromeos4-row1-rack7-host1: RootfsUpdateError: Update failed. The priority of the inactive kernel partition is less than that of the active kernel partition.
11/18 09:23:38.334 INFO |        server_job:0153| END FAIL	86224982-chromeos-test/chromeos4-row1-rack7-host1/provision_AutoUpdate	provision	timestamp=1479489720	localtime=Nov 18 09:22:00

Comment 1 by skau@chromium.org, Nov 18 2016

In case it's relevant, the DUT:
chromeos4-row1-rack7-host1

Comment 2 by skau@chromium.org, Nov 18 2016

It's possible devserver threw an error.

11/18 09:14:11.965 DEBUG|        dev_server:1813| Failed to trigger auto-update process on devserver

This looks like the failing url:
http://100.115.219.132:8082/get_au_status?build_name=wolf-tot-paladin/R56-9001.0.0-rc2&force_update=True&pid=21428&host_name=chromeos4-row1-rack7-host1&full_update=False

11/18 09:14:00.314 DEBUG|        dev_server:1751| Current CrOS auto-update status: rootfs update
11/18 09:14:10.322 DEBUG|        base_utils:0185| Running 'ssh 100.115.219.132 'curl "http://100.115.219.132:8082/get_au_status?build_name=wolf-tot-paladin/R56-9001.0.0-rc2&force_update=True&pid=21428&host_name=chromeos4-row1-rack7-host1&full_update=False"''
11/18 09:14:11.965 DEBUG|        dev_server:1813| Failed to trigger auto-update process on devserver
11/18 09:14:11.966 DEBUG|        base_utils:0185| Running 'ssh 100.115.219.132 'curl "http://100.115.219.132:8082/handler_cleanup?pid=21428&host_name=chromeos4-row1-rack7-host1"''
11/18 09:14:13.634 DEBUG|        base_utils:0185| Running 'ssh 100.115.219.132 'curl "http://100.115.219.132:8082/collect_cros_au_log?pid=21428&host_name=chromeos4-row1-rack7-host1"''
11/18 09:14:15.410 DEBUG|        dev_server:1645| Saving auto-update logs into /usr/local/autotest/results/hosts/chromeos4-row1-rack7-host1/2121595-provision/20161811090821/autoupdate_logs/CrOS_update_chromeos4-row1-rack7-host1_21428.log
11/18 09:14:15.411 DEBUG|        dev_server:1889| Exception raised on auto_update attempt #1:
 Traceback (most recent call last):
  File "/home/chromeos-test/chromiumos/src/platform/dev/cros_update.py", line 222, in TriggerAU
    self._RootfsUpdate(chromeos_AU)
  File "/home/chromeos-test/chromiumos/src/platform/dev/cros_update.py", line 153, in _RootfsUpdate
    cros_updater.PostCheckRootfsUpdate()
  File "/home/chromeos-test/chromiumos/chromite/lib/auto_updater.py", line 926, in PostCheckRootfsUpdate
    raise RootfsUpdateError('Update failed. The priority of the inactive '
RootfsUpdateError: Update failed. The priority of the inactive kernel partition is less than that of the active kernel partition.

Comment 3 by skau@chromium.org, Nov 18 2016

Cc: pgeorgi@chromium.org pprabhu@chromium.org ntang@chromium.org
Status: Fixed (was: Untriaged)

It seems like the update flaked for some reason.  Might want to keep an eye on the host just in case?  I don't that this is a problem right now.

http://cautotest/afe/#tab_id=view_host&object_id=1469