Don't create retirement tasks for things that are already retired #18895
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We shouldn't create tasks for already retired VMs.
bz is https://bugzilla.redhat.com/show_bug.cgi?id=1720338
This is ugly but it'll work for now. The refactor ideally involves using the general status check that Lucy's working on, but until that's baked in and finished and well-tested, we have to do something kinda hacky like this. This check doesn't belong inside the retireable? mixin check because that was intended as a class check for, can this class of thing actually be retired? So since this is an instance method check, it has to be here for now.