Add hqakm and i55je API boundary nodes to mainnet rollout plan - #226
Merged
Conversation
These two API boundary nodes (added 2026-05-04) were never in the mainnet DEFAULT_API_BOUNDARY_NODES_ROLLOUT_PLANS list, so the weekly auto-compute rollout never updated them. They were only bumped via one-off 2-node proposals on an irregular cadence, and lagged ~3 weeks on 62e841d27ea1..., long enough for that version to age out of the release controller's active window while still in use — which broke the GuestOS election (failed proposals 142125 and 142145, registry replica_version invariant). Adding them to the list so they roll forward weekly with the rest.
pietrodimarco-dfinity
enabled auto-merge
June 9, 2026 08:00
r-birkner
approved these changes
Jun 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Add the two API boundary nodes to the mainnet
DEFAULT_API_BOUNDARY_NODES_ROLLOUT_PLANSlist indags/defaults.py(kept in sorted order, betweenek6px…andjlifv…):hqakm-buvkm-5onrb-4ja5j-pne2h-mnlgv-ei4sf-nqn7l-3ir4g-z6xq5-zqei55je-j5vzn-z4odr-yhmrb-nlf46-gbgfg-6uk5e-gssxu-b7hmf-ntlay-pqeList goes from 20 → 22 nodes (matching the live registry's API boundary node count).
Why
These two nodes were added as API boundary nodes on 2026-05-04 but were never in the auto-compute rollout list, so
auto_compute_rollout_to_mainnetnever updated them. They were only bumped by one-off 2-node proposals on an irregular cadence (DeployGuestosToSomeApiBoundaryNodes: 141781 on 2026-05-18 →62e841d…, then nothing until 142146 on 2026-06-09 →a47e5434…).That ~3-week gap left them on
62e841d…(rc--2026-05-07) long enough for it to age out of the release controller's active window while still in use. The release controller's unelect logic doesn't account for API-boundary-node versions, so it tried to retire62e841d…while these nodes still ran it — failing the GuestOS election twice (NNS proposals 142125 and 142145, registryreplica_versioninvariant).Folding them into the weekly rollout keeps them current so this can't recur.
Test plan
DEFAULT_API_BOUNDARY_NODES_ROLLOUT_PLANS["mainnet"]parses as valid YAML with 22 unique, sorted node IDs (verified locally).auto_compute_rollout_to_mainnetrun includes both nodes in the API boundary nodes rollout.Note
Reminder per
dags/defaults.pydocstring: changing defaults may require hitting the reload button on the Airflow DAGs screen for the new defaults to take effect.