Mechanism for blocking nodowntime rollouts on a given bug

Bug #790645 reported by Tom Haddon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
High
Unassigned

Bug Description

If we have to cowboy a change to a specific server that's part of the "nodowntime" deployment alias for some reason, it'd be nice to have a tag that could be associated with the bug that fixes the need for that cowboy such that we could know that we can't rollout to "nodowntime" until it's fixed. If this tied into https://devpad.canonical.com/~lpqateam/qa_reports/deployment-stable.html this would mean that it was obvious to everyone that we couldn't have another deployment to nodowntime until that bug was fixed.

Tom Haddon (mthaddon)
tags: added: canonical-losa-lp
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.