Closed Bug 1154027 Opened 10 years ago Closed 7 years ago

File diagnostics bugs directly from slave health

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: coop, Unassigned)

Details

(Whiteboard: [buildduty][slavehealth][slaveapi])

It would save many steps (and human-interaction time) if sheriffs and buildduty could file a diagnostic bug against a given machine directly from slave health. The slaveapi workflow would look like this: * disable slave in slavealloc (if not already disabled) * (re)open problem tracking bug for slave * check for existing diagnostics bug, file a new one if doesn't exist or closed. We shouldn't re-open an existing diagnostics bug because frequency of diagnostic requests is an important metric for overall slave health ** interface should provide a text box for the initial description of the new diagnostics bug * update slavealloc with link to new diagnostics bug
(In reply to Chris Cooper [:coop] from comment #0) > * check for existing diagnostics bug, file a new one if doesn't exist or > closed. We shouldn't re-open an existing diagnostics bug because frequency > of diagnostic requests is an important metric for overall slave health > ** interface should provide a text box for the initial description of the > new diagnostics bug * make slave problem tracking bug depend on the diagnostics bug > * update slavealloc with link to new diagnostics bug * update slavealloc _notes_ for slave with link to new diagnostics bug
Component: Tools → General
Not expecting to work on this tool anymore.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.