m/test/launch/cluster: fix duplicate NodeIDs entries

This code loop looks for any NEW nodes and inserts them into
cluster.{Nodes,NodeIDs}. The first structure is a lookup from NodeID to
node information, the latter is a list of NodeIDs used to look up
numeric node IDs (in order of startup/detection) to NodeIDs.

The loop in the code runs multiple times to catch any NEW nodes might
take a while to appear, and exits once the expected number of nodes have
been detected.

The bug caused the code to repeatedly insert into Nodes[NodeID] (which
is fine, but wasteful) and into NodeIDs. The latter resulted in a
NodeIDs that contained duplicate entries.

To make sure we only handle each NEW node once, we skip nodes that have
already been seen.

This bug caused us to sometimes act on wrong nodes in E2E tests (any
time tests were looking up node number -> node ID -> Node via .NodeIDs
and .Nodes, they had a chance of picking the wrong node ID / node for a
given node number).

Change-Id: Ie459c8277c0d03902ce23f3b20b0c4e367cc015b
Reviewed-on: https://review.monogon.dev/c/monogon/+/2881
Tested-by: Jenkins CI
Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
1 file changed
tree: d927065d7f56bc46207a9df2c60c9c580757e5dd
  1. .github/
  2. build/
  3. cloud/
  4. go/
  5. intellij/
  6. metropolis/
  7. net/
  8. third_party/
  9. tools/
  10. version/
  11. .bazelignore
  12. .bazelproject
  13. .bazelrc
  14. .bazelrc.ci
  15. .bazelrc.sandboxroot
  16. .bazelversion
  17. .git-ignore-revs
  18. .gitignore
  19. BUILD.bazel
  20. CODING_STANDARDS.md
  21. go.mod
  22. go.sum
  23. LICENSE
  24. MODULE.bazel
  25. MODULE.bazel.lock
  26. README.md
  27. SETUP.md
  28. shell.nix
  29. WORKSPACE
README.md

Monogon Monorepo

This is the main repository containing the source code for the Monogon Platform.

This is pre-release software - take a look, and check back later!

Environment

Our build environment is self-contained and requires only minimal host dependencies:

  • A Linux machine or VM.
  • Bazelisk >= v1.15.0 (or a working Nix environment).
  • A reasonably recent kernel with user namespaces enabled.
  • Working KVM with access to /dev/kvm (if you want to run tests).

Our docs assume that Bazelisk is available as bazel on your PATH.

Refer to SETUP.md for detailed instructions.

Monogon OS

The source code lives in //metropolis (Metropolis is the codename of Monogon OS).

See the //metropolis/README.md for a developer quick start guide, or see the Monogon OS Handbook for user documentation.