Conversation
MCK 1.6.2 Release NotesBug Fixes
|
nammn
added
the
skip-changelog
nammn
commented
Jan 5, 2026
| # to verify the actual public release path. | ||
| # IMPORTANT: Don't use ECR for legacy operator versions (e.g., 1.27.0) because they use | ||
| # different image tag formats that only exist on quay.io, not in ECR. | ||
| build_scenario = operator_installation_config.get("buildScenario", "") |
Collaborator
Author
There was a problem hiding this comment.
helm charts: priorly failing now passing using ecr:
mongodb-ops-manager:
Container ID: containerd://5411883ed7f4acacc6af22072e10e5fd2acbd577442de93ad57edab9f7309f7a
Image: 268558157000.dkr.ecr.us-east-1.amazonaws.com/dev/mongodb-enterprise-ops-manager-ubi:7.0.21
m1kola
approved these changes
Jan 5, 2026
Contributor
m1kola
left a comment
m1kola
left a comment
There was a problem hiding this comment.
Looks good in general, but I'm raising a question/point of caution.
nammn
commented
Jan 5, 2026
| variant: init_test_run | ||
| # Wait for OM images to be published to quay.io on commit builds (staging). | ||
| # On patch builds, this dependency is skipped (task doesn't exist). | ||
| - name: release_om_and_agents |
Collaborator
Author
There was a problem hiding this comment.
this and on other places should ensure that this task runs on master merges first before running the tests, at the same time it won't run on patches as the task doesn't exist (hence the optional setting)
nammn
changed the title
viveksinghggits
approved these changes
Jan 6, 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
5 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.
Summary
This PR fixes upgrade/OLM tests failing in patch builds when testing unreleased OpsManager versions (e.g., 7.0.21) that don't exist on quay.io yet.
Problem
When PR #648 bumped OM from 7.0.20 to 7.0.21, upgrade tests started failing with:
Root Cause: In patch builds, images are published to ECR (dev registry) but not yet to quay.io. Upgrade tests install released operators (from official Helm charts or OLM) which default to quay.io registries.
Solution
Pass ECR registry configuration to upgrade tests in patch builds:
Helm-based Upgrade Tests (
install_official_operator)registry.opsManager): Passed to ALL operators (including legacy like 1.27.0, 1.32.0) because OM version tags are standard (e.g.,7.0.21)registry.agent): Only passed to current/dev operator, NOT legacy operators because they use different tag formats (e.g.,13.21.0.9059-1_1.27.0) that don't exist in ECROLM Upgrade Tests (subscription config)
get_registry_env_vars_for_subscription()helper inolm_test_commons.pyOPS_MANAGER_IMAGE_REPOSITORYenv var (not agent registry) because:Proof of Work
Checklist
skip-changeloglabel if not needed