New issue
Advanced search Search tips

Issue 856329 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: ----



Sign in to add a comment

test_push is broken: cipd fails: "chromiumos/infra/skylab-inventory" doesn't have instance with version "staging".

Project Member Reported by xixuan@chromium.org, Jun 25 2018

Issue description

Notice: /Stage[main]/Profiles::Base::Infra_tools/Cipd[/opt/infra-tools]/Exec[CIPD ensure in /opt/infra-tools]/returns: Error: resolving package: failed to resolve package version (line 2): package "chromiumos/infra/skylab-inventory" doesn't have instance with version "staging".
Error: /opt/infra-tools/.cipd/cipd_v_7d61db0122787613facb00390435a5438b4475ac ensure -root /opt/infra-tools -list /opt/infra-tools/.cipd/tmp/ensure_packages -service-url https://chrome-infra-packages.appspot.com returned 1 instead of one of [0]
Error: /Stage[main]/Profiles::Base::Infra_tools/Cipd[/opt/infra-tools]/Exec[CIPD ensure in /opt/infra-tools]/returns: change from notrun to 0 failed: /opt/infra-tools/.cipd/cipd_v_7d61db0122787613facb00390435a5438b4475ac ensure -root /opt/infra-tools -list /opt/infra-tools/.cipd/tmp/ensure_packages -service-url https://chrome-infra-packages.appspot.com returned 1 instead of one of [0]


 
Cc: -ayatane@chromium.org pprabhu@chromium.org
Owner: ayatane@chromium.org
Owner: pprabhu@chromium.org
Status: Started (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Jun 25 2018

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

commit 99d392e53de1d71d06e74cb2cd03661665ed754f
Author: Prathmesh Prabhu <pprabhu@chromium.org>
Date: Mon Jun 25 21:02:50 2018

Cc: ayatane@chromium.org
Fixed manually by adding staging ref.

This was jammed on the recurring flavored issue of sync being broken and thus unable to get the fix.
Re #6 I take that back, it's not that bad, we would have just needed to run test_push twice, since it updates itself as part of the test_push, but it needs another run to actually pick up the fix to itself.

It's still possible for it to break its own sync though.
Status: Fixed (was: Started)
Re #7, yep I'd realized that after hours.

Sign in to add a comment