859403 - File slave bugs automatically for known failure cases

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Chris Cooper [:coop] (he/him)]

When we reach the end of certain code paths in kittenherder, we *know* that the next step is filing a bug to recover the slave, e.g. a talos-r3 machine is unpingable.

There's no sense in waiting for a human to notice that. kittenherder (or replacement) should file that bug (and do the associated dance with the appropriate reboots bug) automatically.

catlee already has some code to do this:

https://github.com/catlee/relengbot/blob/master/relengbot/slave_bugger.py

Comment 1

[Armen [:armenzg]]

For some reason this bug is marked as a goal.
"[ON TRACK] better slave issue tracking bug 859403"

Comment 2

[Chris Cooper [:coop] (he/him)]

(In reply to Armen Zambrano G. [:armenzg] (Release Enginerring) from comment #1)
> For some reason this bug is marked as a goal.
> "[ON TRACK] better slave issue tracking bug 859403"

It's marked as a goal because it's pretty important, and we all agreed to it at the start of the quarter.

Comment 3

[Chris Cooper [:coop] (he/him)]

slaveapi does this now.