Closed Bug 1126928 Opened 10 years ago Closed 7 years ago

slaveapi terminate actions don't appear in the reboot history list

Categories

(Release Engineering :: General, defect)

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

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: coop, Unassigned)

References

Details

(Whiteboard: [buildduty][slavehealth])

In slave health, when I terminate an AWS instance via terminate button on the slave.html page, the reboot history list doesn't include this information. I think it's simply a matter of hitting the terminate GET endpoint for that slave and sorting the data into the list. We should limit this behavior to AWS instances. No sense making the extra call for non-AWS slaves. We should also update the history list when a terminate action finishes and the user is still looking at the page. This should be a simple callback like we do for reboots.
> information. I think it's simply a matter of hitting the terminate GET > endpoint for that slave and sorting the data into the list. yup, that should do it. nothing magical about this endpoint as it should behave like reboot
Blocks: 1045114
Whiteboard: [buildduty][slave health] → [buildduty][slavehealth]
Component: Tools → General
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.