ccompute_config.py generating conflicting IP |
|||||
Issue descriptionccompute_config.py generated an IP that conflicting with an existing instance's IP. Deleting the entry in expectations/swarm.json and re-training generated a new, fortunately unique, IP. This passed the CQ. https://chrome-internal-review.googlesource.com/c/infra/infra_internal/+/582757, see swarm666-c4 and swarm848-c4.
,
Mar 5 2018
104.154.9.225
,
Mar 5 2018
Note that this bug is more about the fact that it passed the CQ.
,
Mar 6 2018
Issue 819049 has been merged into this issue.
,
Mar 6 2018
Is there a work-around? This is blocking me from spawning some machines.
,
Mar 6 2018
Delete the conflicting entry in expectations/swarm.json, retrain, and check --- that's what worked for me.
,
Mar 6 2018
That worked, thnx!
,
Mar 6 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/infra_internal/+/0fa4c3e6b36f5d538ebe72eaa48495b77bcd4dd1 commit 0fa4c3e6b36f5d538ebe72eaa48495b77bcd4dd1 Author: Benjamin Pastene <bpastene@chromium.org> Date: Tue Mar 06 20:22:16 2018
,
Apr 10 2018
Happened again here: https://chrome-internal-review.googlesource.com/c/infra/infra_internal/+/604889 (see IP 104.155.246.21)
,
Apr 10 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/infra_internal/+/40e170c7bb58ccae1a04b68f3cfd994508072b95 commit 40e170c7bb58ccae1a04b68f3cfd994508072b95 Author: Ryan Tseng <hinoka@google.com> Date: Tue Apr 10 18:12:48 2018
,
Jun 16 2018
Ryan, can this be counted as resolved?
,
Jun 16 2018
,
Jun 18 2018
With the check running in CQ and CI, it can be counted as fixed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by friedman@chromium.org
, Mar 5 2018