New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 902811 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 20
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Push a new labstation version with mentioned cl, ref bug b/117848487

Project Member Reported by modia@chromium.org, Nov 7

Issue description

For running the daily cr50 suite at high touch lab, we need a new labstation push

Ref bug: b/b/117848487, please merge all CLs part of this bug and push a new labstation version

suite: http://go/gschightouch

Deputy to push new labstation version. 
 
Labels: -Pri-0 Pri-1
Cc: zamorzaev@chromium.org
Owner: zamorzaev@chromium.org
Status: Assigned (was: Untriaged)
Alex is working on a tool to manually push labstation updates.
He can use this bug as a testing ground for the tool.
Status: Started (was: Assigned)
Does R72-11239.0.0 (the latest green guado_labstation-release
builder) contain all the fixes to b/117848487? Is there any additional testing I should do before deploying it?
It should yeah. I don't think it should require more testing than just making sure deploy servo works as expected (essentially, the issue we had last time shouldn't reoccur)
Any update on the labstation push? This is blocking cr50 qual.
Labels: Hotlist-Deputy
I will do it once the lab fully recovers from issue 903988.
That bug says "The current plan is to wait for a couple of days and investigate whether the inconsistency is small and that replicas are safe to use."

Does that mean there won't be a labstation push this week?
That's referring to the long term resolution of the underlying issue. 

There was a temporary solution applied and I verified that the lab has been stable. I am planning to kick off the labstation update today. 

Is R72-11239.0.0 still a good version to use? Or do you want me to use the latest green version - R72-11245.0.0?
I tested that updated to and from R72-11245.0.0 works and set it as the stable version. I will start the semi-manual labstation update now.

zamorzaev@zamorzaev:~/chromiumos$ stable_version -t cros guado_labstation R72-11245.0.0
Updating  Chrome OS  guado_labstation -> R72-11170.0.0 to R72-11245.0.0
Unchanged Firmware   guado_labstation -> Google_Guado.6301.108.2016_10_06_1219
does the semi-manual update include chromeos1 labstations? background: looking to get chromeos1-row1-rack5-labstation, chromeos1-row2-rack1-labstation, chromeos1-row2-rack10-labstation to R72-11245.0.0 (even more background go/fwcr50qual)


If chromeos1 is not included, would running "update_engine_client --update" be the optimal way to pick up the update on the chromeos1 labstations?
chromeos1-row1-rack5-labstation and chromeos1-row2-rack10-labstation are still running the old release, so modia@ is going to poke at getting them updated.
(chromeos1-row2-rack1-labstation is on the new release)
Status: Fixed (was: Started)
The labstations in chromeos2,4,6 have been updated.

Sign in to add a comment