1023502 - slaveapi disable - comment in bug while disabling is in progress and add a reason dep bug option

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Jordan Lund (:jlund)]

+++ This bug was initially created as a clone of Bug #932396 +++

now that slaveapi can disable bugs, let's refine its features.

- It would be nice to comment in the tracking bug immediately once disable was called as sometimes disabling can take a while if we are not using force.

- On top of adding a reason comment, we should be able to add a reason bug # that gets added to the problem tracking list of dep bugs. This would be good for pointing to loaning bugs, infra failure bugs, etc

Comment 1

[Jordan Lund (:jlund)]

slaveapi should also update the 'notes' column in slavealloc to whatever 'reason' was, if reason was given.

Comment 2

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

(In reply to Jordan Lund (:jlund) from comment #0)
> - It would be nice to comment in the tracking bug immediately once disable
> was called as sometimes disabling can take a while if we are not using force.

That's a lot of unnecessary bug update churn IMO. I do think we should leverage the notes field more. The tools already look up the tracking bug automatically, so we don't need the bug number in the status field, but having the last action plus timestamp in the notes field would be really beneficial.

> - On top of adding a reason comment, we should be able to add a reason bug #
> that gets added to the problem tracking list of dep bugs. This would be good
> for pointing to loaning bugs, infra failure bugs, etc

I think I understand what you're saying here and fully agree: the notes field should be for meta-bug information, not the machine tracking bug. Our alias naming convention for the tracking bugs obviates the need for the tracking bug.

Comment 3

[Justin Wood (:Callek)]

Not expecting to work on this tool anymore.