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

Issue 833442 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
OOO
Closed: Dec 5
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: ----



Sign in to add a comment

devserver provision: using same git hash of chromite with other devservers

Project Member Reported by xixuan@chromium.org, Apr 16 2018

Issue description

Based on https://viceroy.corp.google.com/chromeos/deputy-view, Production git hash of chromite, there's one server's chromite version is different. Due to http://shortn/_pikX6c4IZf, it's chromeos2-devserver8. 

Assign to secondary to check whether this server doesn't get properly updated.
 

Comment 1 by gu...@chromium.org, Apr 16 2018

Owner: shuqianz@chromium.org
Summary: devserver provision: using same git hash of chromite with other devservers (was: chromeos2-devserver8 is not updated with other devservers)
The git hash of chromeos2-devserver8 is newer than others. This should because it is a newly provisioned devserver. see https://buganizer.corp.google.com/issues/73135917#comment11

Thus, the problem should be, when provision a new devserver, we should use same git hash of dev-util, chromite, etc. as other devserver, instead of the latest.

Owner: gu...@chromium.org
guocb@, since you are working on devserver related works, I think you can take this bug to get familiar with how a new devserver is provisioned, how the devserver gets updated. It is an easy bug but it can help you get speed up :)
Project Member

Comment 3 by bugdroid1@chromium.org, Dec 5

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/912dffd926ba8fa436152354255354bfd7cbed77

commit 912dffd926ba8fa436152354255354bfd7cbed77
Author: Congbin Guo <guocb@chromium.org>
Date: Wed Dec 05 03:09:15 2018

Status: Fixed (was: Assigned)

Sign in to add a comment