860074 - release runner: nice to easily restart from master reconfig

Status: RESOLVED WONTFIX

(Release Engineering :: Release Automation, defect, P3)

Description

[hwine]

For 21.0b2, a couple of masters failed to reconfigure (DNS issue). To fix required backing out the changes and tags on all the pre-sendchange repos. The release itself was automatically "returned" to unreviewed status in ship-it

Especially for when non-committers are running releases, it'd be great to have something that would allow retries from ship-it.

Perhaps either:
 - an explicit "restart from reconfig" action in ship-it, or
 - release-runner smart enough to "do the right thing" when the same release is re-reviewed prior to the sendchange being sent.

At the least, a "why did the release return to the to-be-reviewed section" FAQ entry would be useful.

Comment 1

[[e-mail] (:bhearsum)]

I agree, we need to improve here. bug 847424 would probably fix this.

(In reply to Hal Wine [:hwine] from comment #0)
> At the least, a "why did the release return to the to-be-reviewed section"
> FAQ entry would be useful.

What was in the Status field after the release got punted back?

Comment 2

[hwine]

(In reply to Ben Hearsum [:bhearsum] from comment #1)
> What was in the Status field after the release got punted back?

I don't recall seeing a status field in the "to be reviewed" view. If it's there, I did not take note of the contents.

It'd be fancy CSS work, but maybe a different color text for "not good end state" status messages?

Comment 3

[[e-mail] (:bhearsum)]

(In reply to Hal Wine [:hwine] from comment #2)
> (In reply to Ben Hearsum [:bhearsum] from comment #1)
> > What was in the Status field after the release got punted back?
> 
> I don't recall seeing a status field in the "to be reviewed" view. If it's
> there, I did not take note of the contents.

Hm, looks like we don't show that there...that's bad.

> It'd be fancy CSS work, but maybe a different color text for "not good end
> state" status messages?

Yeah, I think we can do something to make these messages more noticeable when we get into this state.

Comment 4

[[e-mail] (:bhearsum)]

(In reply to Ben Hearsum [:bhearsum] from comment #3)
> (In reply to Hal Wine [:hwine] from comment #2)
> > (In reply to Ben Hearsum [:bhearsum] from comment #1)
> > > What was in the Status field after the release got punted back?
> > 
> > I don't recall seeing a status field in the "to be reviewed" view. If it's
> > there, I did not take note of the contents.
> 
> Hm, looks like we don't show that there...that's bad.
> 
> > It'd be fancy CSS work, but maybe a different color text for "not good end
> > state" status messages?
> 
> Yeah, I think we can do something to make these messages more noticeable
> when we get into this state.

This is a separate issue, filed it in bug 860290.

Comment 5

[Rail Aliiev [:rail]]

No more reconfigs!