Skip to content

fix(runners): temporarily reduce mac-finch-15-arm desired to 1 to unblock Prod wave - #1115

Merged
coderbirju merged 1 commit into
mainfrom
reduce-mac15-arm-desired-to-1
Sep 4, 2026
Merged

coderbirju merged 1 commit into
mainfrom
reduce-mac15-arm-desired-to-1

Conversation

@coderbirju

@coderbirju coderbirju commented Sep 4, 2026 •

Copy link
Copy Markdown
Contributor

Problem

FinchPipeline wave.1 is blocked. Production-ASG-mac-finch-15-armStack fails to deploy: its ASG wants DesiredCapacity=2, but only 1 mac2.metal ARM instance is currently healthy and AWS has Insufficient mac2.metal capacity in us-west-2 to launch the 2nd (all 5 available mac2 hosts are at 0 free capacity; new-host allocation fails).

CloudFormation cannot stabilize, so the stack wedges in UPDATE_ROLLBACK_FAILED, blocking Prod and the downstream Release wave (which carries the Windows update).

Change

This reduces demand to match currently available capacity so the deploy stabilizes on the single instance that already exists, unblocking the wave. No other runner entry is touched (mac 26.3 arm, mac 15.7 x86, windows 2022 x86, and all finch-core entries stay as-is).

Temporary — revert plan

This is temporary. Once mac2.metal capacity is healthy, restore desiredInstances to 2

Note

The already-wedged Production-ASG-mac-finch-15-armStack (UPDATE_ROLLBACK_FAILED) was recovered separately via continue-update-rollback; this PR prevents the ASG from re-wedging on the next deploy.

Testing

  • npm ci — ok
  • npm run build (tsc) — ok
  • npm test (jest unit) — 12 suites / 15 tests passed

No unit test required updating.

…lock Prod wave

mac2.metal ARM capacity in us-west-2 is exhausted: only 1 healthy instance exists and AWS cannot allocate a 2nd (all available mac2 hosts at 0 free capacity). The Production-ASG-mac-finch-15-armStack ASG wants DesiredCapacity=2, so CloudFormation cannot stabilize and the stack wedges (UPDATE_ROLLBACK_FAILED), blocking the Prod wave and the downstream Release wave (which carries the Windows update).

Reduce runnerProd mac/15.7/arm/finch desiredInstances 2 -> 1 to match currently available capacity so the deploy stabilizes on the single existing instance.

TEMPORARY: restore to 2 (and/or rely on the N+1 durability fix in #1113) once mac2.metal capacity is healthy. Complementary to #1113, which ADDS N+1 headroom (needs more capacity); this REDUCES demand to match current capacity.
Signed-off-by: Arjun Yogidas <arjunry@amazon.com>
@coderbirju
coderbirju requested a review from a team as a code owner September 4, 2026 21:52

@sondavidb sondavidb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should revert this once release is unblocked

@coderbirju
coderbirju merged commit b5192ad into main Sep 4, 2026
6 checks passed
@coderbirju
coderbirju deleted the reduce-mac15-arm-desired-to-1 branch September 4, 2026 22:40
coderbirju added a commit that referenced this pull request Sep 10, 2026
…eeping mac2 + no N+1

We revert the mac-m4 switch (#1117) and the N+1/launch-before-terminate capacity change (#1113) and the mac-15-arm desired reduction (#1115) to match available dedicated hosts, but RETAIN the dedicated host (auto-release-host=false) so a replacement instance relaunches onto the same held host instead of re-allocating a scarce Mac host. Net: mac2.metal, maxCapacity=desired, minInstancesInService=0, auto-release-host=false, mac-15-arm desired=2.

Signed-off-by: Arjun Yogidas <arjunry@amazon.com>
coderbirju added a commit that referenced this pull request Sep 10, 2026
…eeping mac2 + no N+1

We revert the mac-m4 switch (#1117) and the N+1/launch-before-terminate capacity change (#1113) and the mac-15-arm desired reduction (#1115) to match available dedicated hosts, but RETAIN the dedicated host (auto-release-host=false) so a replacement instance relaunches onto the same held host instead of re-allocating a scarce Mac host. Net: mac2.metal, maxCapacity=desired, minInstancesInService=0, auto-release-host=false, mac-15-arm desired=2.

Signed-off-by: Arjun Yogidas <arjunry@amazon.com>
coderbirju added a commit that referenced this pull request Sep 10, 2026
…=false) (#1121)

* Revert "fix(runners): move arm macOS runners from mac2.metal to mac-m4.metal (#1117)"

This reverts commit 1bc4a77.

Signed-off-by: Arjun Yogidas <arjunry@amazon.com>

* Revert "fix(runners): make dedicated-host (mac/windows) ASG deploys resilient to metal capacity (#1113)"

This reverts commit 4b0ef9d.

Signed-off-by: Arjun Yogidas <arjunry@amazon.com>

* Revert "fix(runners): temporarily reduce mac-finch-15-arm desired to 1 to unblock Prod wave (#1115)"

This reverts commit b5192ad.

Signed-off-by: Arjun Yogidas <arjunry@amazon.com>

* fix(runners): retain dedicated host (auto-release-host=false) while keeping mac2 + no N+1

We revert the mac-m4 switch (#1117) and the N+1/launch-before-terminate capacity change (#1113) and the mac-15-arm desired reduction (#1115) to match available dedicated hosts, but RETAIN the dedicated host (auto-release-host=false) so a replacement instance relaunches onto the same held host instead of re-allocating a scarce Mac host. Net: mac2.metal, maxCapacity=desired, minInstancesInService=0, auto-release-host=false, mac-15-arm desired=2.

Signed-off-by: Arjun Yogidas <arjunry@amazon.com>

---------

Signed-off-by: Arjun Yogidas <arjunry@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants