Closed Bug 1154032 Opened 5 years ago Closed 4 years ago

File panda-recovery bugs directly from slave health

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: coop, Unassigned)

Details

Similar to bug 1154027, sheriffs and buildduty should be able to file panda-recovery bugs directly from slave health, or associate bad pandas with an existing panda-recovery bug.

slaveapi workflow would look like this:
* disable panda in slavealloc (if not already disabled)
* (re)open problem tracking bug for panda
* check for existing panda-recovery bug, file a new one if doesn't exist or closed. This is standard procedure for panda-recovery bugs, i.e. we don't re-use old ones.
* add panda problem tracking bug as a blocker to the panda-recovery bug
* update slavealloc notes for panda with link to new panda-recovery bug
(In reply to Chris Cooper [:coop] from comment #0)
> * add panda problem tracking bug as a blocker to the panda-recovery bug

Should be:

* block panda problem tracking bug on the panda-recovery bug
No longer using pandas, therefore no need for a panda-recovery bug.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.