deleting and adding host to AFE at inopportune time can leave host in Running state |
|||
Issue description
host in question chromeos6-row1-rack2-host5
mysql> SELECT * FROM afe_hosts WHERE hostname = 'chromeos6-row1-rack2-host5'\G;
*************************** 1. row ***************************
id: 4903
hostname: chromeos6-row1-rack2-host5
locked: 0
synch_id: NULL
status: Running
invalid: 1
protection: 0
locked_by_id: NULL
lock_time: NULL
dirty: 1
leased: 1
shard_id: NULL
lock_reason:
1 row in set (0.00 sec)
When I readd (./atest host create ...) it, it looks like this:
mysql> SELECT * FROM afe_hosts WHERE hostname = 'chromeos6-row1-rack2-host5'\G;
*************************** 1. row ***************************
id: 4903
hostname: chromeos6-row1-rack2-host5
locked: 0
synch_id: NULL
status: Running
invalid: 0
protection: 0
locked_by_id: NULL
lock_time: NULL
dirty: 1
leased: 1
shard_id: NULL
lock_reason:
1 row in set (0.01 sec)
And I can't do anything with it (verify, repair, job). Plus the shard_id should be 116 (chromeos-server70 for celes).
It seems like when a host is deleted, seems like the status field should be reset to 'Repair failed' or 'Ready'.
,
Oct 4 2016
Is there more work needed on this?
,
Oct 11 2016
,
Oct 12 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by kevcheng@chromium.org
, Sep 28 2016