v1.5.16

What's changed

⚠️ Breaking 1. Config schema: apiVersion bumped to v1.6; spec.mcr.version removed

The config API version advances from launchpad.mirantis.com/mke/v1.5 to launchpad.mirantis.com/mke/v1.6.

The spec.mcr.version field is removed. MCR is now selected exclusively by channel, which pins a major.minor release stream and always installs the latest patch in that stream.

Before (v1.5):

apiVersion: launchpad.mirantis.com/mke/v1.5
spec:
  mcr:
    version: "25.0.5"
    channel: stable

After (v1.6):

apiVersion: launchpad.mirantis.com/mke/v1.6
spec:
  mcr:
    channel: stable-25.0

Launchpad includes an automatic migration: configs with apiVersion: launchpad.mirantis.com/mke/v1.5 are migrated transparently on load by combining the old channel and version values into the new channel format (e.g. stable + 25.0.5 → stable-25.0). Run launchpad describe config after first use to inspect the migrated form.

---

2. Linux MCR installation method changed (no more install.sh)

MCR on Linux is now installed via native OS package managers (apt/yum/zypper) instead of the https://get.mirantis.com/ shell script. This removes the spec.mcr.installScriptRemoteDirLinux config field (it is accepted but ignored).

The MCRInstallURLLinux constant and the download phase have been removed entirely. The installURLWindows field and Windows installer path are unchanged.

Impact: Hosts that previously blocked outbound access to get.mirantis.com but allowed access to repos.mirantis.com will now work without requiring the install-script URL. Hosts that blocked repos.mirantis.com will now fail where they previously succeeded.

---

3. SSH key resolution: keyPath now takes priority over ssh-agent

Updated to rig v0.21.2. When spec.hosts[*].ssh.keyPath is set, it is now used instead of any keys offered by the local SSH agent. Previously the agent could override keyPath.

Impact: If you previously relied on the agent to supply a different key than keyPath, that key will no longer be used. Remove keyPath from the config or clear the agent to restore prior behaviour.

---

4. Windows MCR install: exit code 3010 now triggers a reboot instead of failing

The Windows MCR installer can exit with code 3010 (ERROR_SUCCESS_REBOOT_REQUIRED) to signal a pending reboot. Previously Launchpad treated this as a failure. It is now correctly interpreted as success-with-reboot, and Launchpad will reboot the node and continue.

Impact: Existing pipelines that caught and handled the exit-3010 failure externally should be reviewed — the reboot now happens automatically inside Launchpad.

Changelog

• PRODENG-3238 test and example product version update by @james-nesbitt in #601
• PRODENG-3202 Migrate from msr.ci to registry.ci by @pgedara in #600
• PRODENG-3100 GHA updates by @james-nesbitt in #606
• PRODENG-3100 updates and linting (before ticket) by @james-nesbitt in #605
• PRODENG-3100 Linux native MCR install by @james-nesbitt in #608
• PRODENG-3325-mke-repo-with-colon-port by @james-nesbitt in #607
• docs: restructure documentation for AI agent optimization by @james-nesbitt in #612
• Migrate to gha only by @james-nesbitt in #615
• fix: update rig to v0.21.2 to prioritize keyPath over ssh-agent by @james-nesbitt in #618
• Release checksums and legacy asset filenames by @james-nesbitt in #619
• fix: inject version and commit via ldflags in CI builds by @james-nesbitt in #621
• chore: update golang to 1.26 and GHA to latest versions by @james-nesbitt in #622
• ENGINE-1383: Handle Windows exit code 3010 and fix reboot after MCR install by @james-nesbitt in #624
• windows configurer: remove pre-delete race from Reboot() by @james-nesbitt in #626
• smoke tests: replace small/full with modern/legacy/windows by @james-nesbitt in #627

Full Changelog: v1.5.15...v1.5.16