smoke: add TestCuttingEdgeCluster (rhel10/rocky10/ubuntu24/sles15)#642
Open
james-nesbitt wants to merge 5 commits into
Open
smoke: add TestCuttingEdgeCluster (rhel10/rocky10/ubuntu24/sles15)#642james-nesbitt wants to merge 5 commits into
james-nesbitt wants to merge 5 commits into
Conversation
Adds a new smoke test targeting the latest gen-10 distributions: - RHEL 10, Rocky 10, Ubuntu 24.04 as managers and workers - SLES 15 as an additional worker Also adds: - Rhel10 and Rocky10 platform definitions in test/platforms.go - smoke-cutting-edge Makefile target (50m timeout) - smoke-cutting-edge CI job triggered by the smoke-cutting-edge label NOTE: This test depends on terraform-mirantis-modules/terraform-mirantis-provision-aws PR #22 being merged (adds rhel_10 and rocky_10 platform keys to the provision-aws module). The test will fail until the module is updated and the version bumped in examples/terraform/aws-simple/. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Signed-off-by: James Nesbitt <jnesbitt@mirantis.com>
- shorten Name "cutting-edge" -> "cuttingedge" (11 chars): the 12-char
value overflowed the 32-char AWS LB/target-group name limit and was
the actual CI failure ("name" cannot be longer than 32 characters)
- pin examples/terraform/aws-simple to provision-aws >= 0.1.7, which
ships the rhel_10/rocky_10 platform keys (provision-aws#22, released)
- refresh test doc comment now the upstream dependency is merged/released
gofmt also normalized two pre-existing violations in smoke_test.go.
rhel10/rocky10 AMIs and provision-aws platform keys (v0.1.7) are already available, but launchpad's own smoke coverage previously failed with 'package manager could not install docker-ee' because repos.mirantis.com had not yet published docker-ee for rhel/10 or rocky/10. Checked repos.mirantis.com directly: docker-ee is now present in both rhel/10/x86_64/stable-29.4 and rocky/10/x86_64/stable-29.4 -- that gap looks closed, matching the AMI-availability timing pattern seen elsewhere this cycle (Oracle Linux, Rocky 8). Strategy going forward: keep TestCuttingEdgeCluster merged and label-gated rather than blocking on it going green immediately, so it picks up MCR support automatically as soon as it lands, with no further code changes. Documented that intent on the Makefile target and the GitHub Actions job. Written by AI: claude-sonnet-5
james-nesbitt
force-pushed
the
smoke/cutting-edge-test
branch
from
July 22, 2026 07:24
093c76b to
d1a9f2d
Compare
Adds a Sles16 platform definition (sles_16) and switches TestCuttingEdgeCluster's additional worker from sles15 to sles16. NOTE: MCR has not published Docker EE packages for SLES 16 as of 2026-07-22 (repos.mirantis.com/sles/ only has 12/12.3/15). This node is expected to fail at Install MCR until MCR ships SLES16 support - same category of gap as RHEL10/Rocky10 (docker-ee installs but the daemon won't start), tracked separately for that pair. Flagged in a doc comment on the test so CI failures here are understood, not mysterious. gofmt also cleaned two pre-existing, unrelated violations in these files (trailing blank line in platforms.go; WrkWin2025 alignment in TestFIPSCluster).
Adds a Ubuntu26 platform definition (ubuntu_26.04, codename resolute) and switches TestCuttingEdgeCluster's Ubuntu manager+worker from 24.04 to 26.04 - the current LTS as of 2026-07 (24.04 remains fully supported, just no longer the newest release). The ubuntu_26.04 key is already present in the pinned provision-aws module (>= v0.1.7), AMI pattern confirmed against a live published AMI (ubuntu-resolute-26.04-amd64-server-*, published as recently as 2026-07-22). NOTE: MCR has not published Docker EE packages for Ubuntu 26.04 yet (repos.mirantis.com/ubuntu/dists/ only has trusty/xenial/bionic/focal/ jammy/noble - no resolute). This node is expected to fail at Install MCR alongside the existing SLES16 and RHEL10/Rocky10 gaps, until MCR ships support. Flagged in the test's doc comment.
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
1 participant
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.
Summary
TestCuttingEdgeClustersmoke test targeting gen-10 distributions: RHEL 10, Rocky 10, Ubuntu 24.04 as managers and workers, with SLES 16 as an additional workerRhel10,Rocky10, andSles16platform definitions totest/platforms.gosmoke-cutting-edgeMakefile target (50m timeout)smoke-cutting-edgeCI job triggered by thesmoke-cutting-edgelabelThis test targets the newest OS releases ahead of MCR packaging/support. As of 2026-07-22, MCR does not fully support most of these platforms yet, so
smoke-cutting-edgeis expected to fail and should not be used as a merge gate or general-purpose smoke check. It exists to track forward-looking coverage and will go green incrementally as MCR ships support for each platform below.docker-ee-29.4.1m1-1.el10)systemctl start dockerfails after a clean install; confirmed 100% reproducible across 2 independent CI runs (2026-06-08, 2026-07-22). MCR product gap, not a launchpad bug — root cause not yet isolated (stderr suppressed by the install command).repos.mirantis.com/sles/only has12/,12.3/,15/. Fails immediately at the Install MCR phase.Net effect: of the 7 nodes in
TestCuttingEdgeCluster(3 managers + 4 workers), only the Ubuntu 24.04 nodes currently install successfully. RHEL 10, Rocky 10, and SLES 16 will all fail the Install MCR phase until MCR addresses the gaps above.Platform / dependency history
rhel_10/rocky_10platform keys — merged, andexamples/terraform/aws-simple/is now pinned to>= 0.1.7, which includes them.Test plan
examples/terraform/aws-simple/smoke-cutting-edgelabel to this PR to trigger the CI jobsmoke-cutting-edgegoes green per-platform as each MCR gap is closedWritten by AI: claude-opus-4-8