Page MenuHomePhabricator

scap deploy-promote uses latest train blocker, which is wrong if a train has been blocked over the weekend
Open, LowPublicBUG REPORT

Description

From train operations this morning, after T330213: 1.41.0-wmf.7 deployment blockers sat at group1 over the weekend:

14:42:27 brennen@deploy1002 ~ $ scap deploy-promote group2 1.41.0-wmf.7                                                                                                                     
Promote group2 from 1.41.0-wmf.6 to 1.41.0-wmf.7 (y/n): y

Resulting in log messages on T330214: 1.41.0-wmf.8 deployment blockers: T330214#8833572

This is a rare case (and hopefully rarer as time goes on), but it does come up occasionally.

Event Timeline

brennen updated the task description. (Show Details)

Note that this differs from a case where, e.g., we just haven't resolved the previous train blocker task. That is: We can't rely on task status for this.

Sandeeps changed the task status from Open to In Progress.Jan 16 2024, 2:48 PM
Sandeeps changed the task status from In Progress to Open.