Fix install/upgrade doc gaps and wrong mke3-upgrade image found durin… - #30
Draft
sgajlekar-spec wants to merge 1 commit into
Draft
Fix install/upgrade doc gaps and wrong mke3-upgrade image found durin…#30sgajlekar-spec wants to merge 1 commit into
sgajlekar-spec wants to merge 1 commit into
Conversation
…g manual e2e validation Manual testing of provision/install/no-touch-join/upgrade surfaced several issues: install-bootc-mke3.md and upgrade-bootc-mke3.md missed that ansible-playbook must run from ansible/ to pick up ansible.cfg (host_key_checking), and install-bootc-mke3.md was missing the GNU tar (macOS), kubectl/helm, and WSL (Windows) prerequisites for the controller running the playbooks. Separately, MKE3_UPGRADE_IMAGE's default (bootc-mke3/mke3-upgrade:latest) doesn't exist in the registry, causing every mke3-verify-environment job to ImagePullBackOff and look hung for the full 900s job deadline instead of failing fast; corrected to the actual image documented in cluster-upgrade-controller's own docs. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
sgajlekar-spec
pushed a commit
to sgajlekar-spec/bootc-mke3
that referenced
this pull request
Aug 3, 2026
…dings Live-tested against a real ClusterUpgrade after patching the controller to 0.1.4 (clearing PRODENG-3570's original stall): SUC correctly created the verify-environment Plan/Job on all 3 nodes this time, but every pod hit ErrImagePull -- 'failed to resolve reference registry.mirantis.com/bootc-mke3/mke3-upgrade:latest: ... not found'. The CR burned its full 4h internal timeout retrying before reporting Failed. The mke3-upgrade job image is published under the cluster-upgrade-controller registry project (matching that repo's own release.yml), not bootc-mke3/. Confirmed live: registry.mirantis.com/cluster-upgrade-controller/mke3-upgrade:latest pulls fine and is already preloaded on nodes by mke-images.service (no network needed on a default install) -- the old bootc-mke3/ path is not a typo of a real path, it simply does not exist. - 01-discover.sh: fix MKE3_UPGRADE_IMAGE default. - SKILL.md: document the image-path bug, the now-merged PR Mirantis#23 chart-fetch fix's effect on the AMI-rebuild gotcha, and cluster-upgrade-controller v0.1.4's separate values.yaml image-tag defect (PR Mirantis#30, pending). Written by AI: claude-opus-4-8
sgajlekar-spec
force-pushed
the
PRODENG-3608-e2e
branch
from
August 3, 2026 22:52
7e9a605 to
968c1dc
Compare
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.
…g manual e2e validation
Manual testing of provision/install/no-touch-join/upgrade surfaced several issues: install-bootc-mke3.md and upgrade-bootc-mke3.md missed that ansible-playbook must run from ansible/ to pick up ansible.cfg (host_key_checking), and install-bootc-mke3.md was missing the GNU tar (macOS), kubectl/helm, and WSL (Windows) prerequisites for the controller running the playbooks. Separately, MKE3_UPGRADE_IMAGE's default (bootc-mke3/mke3-upgrade:latest) doesn't exist in the registry, causing every mke3-verify-environment job to ImagePullBackOff and look hung for the full 900s job deadline instead of failing fast; corrected to the actual image documented in cluster-upgrade-controller's own docs.