NO-ISSUE: rebase 5.0 with metrics-client-ca fix - #7418
redhat-chai-bot wants to merge 95 commits into
Conversation
The docker.io/nginxinc/nginx-unprivileged:latest image is a multi-arch manifest list with 14 platform variants. When mirroring with `skopeo copy --all --preserve-digests`, Quay v3.11.7 rejects one of the platform manifests as "manifest invalid", causing the mirror step to fail and aborting CI jobs (e.g. e2e-aws-tests-arm). These test pods only run `sleep 1d` and do not use any nginx functionality, so replace the image with quay.io/microshift/busybox:1.36 which is already mirrored as a single-arch image. This eliminates the problematic multi-arch manifest list from the mirror set entirely. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The busybox image does not include /bin/bash. The Oc Exec Robot keyword hardcoded /bin/bash -c for oc exec commands, causing failures when exec'ing into busybox-based pods. Switch to /bin/sh which is available in all containers and sufficient for the POSIX commands used in tests (echo, cat, ls, grep, etc.). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…rry-pick-7199-to-release-5.0 [release-5.0] USHIFT-7451: replace nginx-unprivileged with busybox in test assets
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
…0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18_arm64-2026-08-18 NO-ISSUE: rebase-release-5.0.0-0.nightly-2026-08-18-203845_amd64-2026-08-18-145649_arm64
…rry-pick-7224-to-release-5.0 [release-5.0] USHIFT-7465: Fix issue filtering for rebase
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
USHIFT-7487: bump cri-o version to 5.0 according to art new builds
USHIFT-7488: Fix repo priority when building from sources in configur…
…2026-08-30_arm64-2026-08-30 (openshift#7279) * update last_rebase.sh * update changelog * update component images * update manifests * update buildfiles * update cbom * Update AI Model Serving for MicroShift * Update SR-IOV for MicroShift --------- Co-authored-by: microshift-rebase-script[bot] <114237296+microshift-rebase-script[bot]@users.noreply.github.com>
The cri-o package was rebranded from 1.36.x to 5.0.0 versioning, making the ec.6 RPMs on the dev-preview mirror unsatisfiable (requires cri-o >= 1.36.0, < 1.37.0 but only 5.0.0 is available). Point to the RC mirror where rc.0 RPMs have correct dependencies. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> pre-commit.check-secrets: ENABLED
The gitops repo advanced to 1.21, causing the manage_common_versions.sh verify step to reject the stale 1.19 value. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> pre-commit.check-secrets: ENABLED
Add ostree (.toml) and bootc (.containerfile) image blueprints for RHEL 9.8 with y-1 (4.22) and y-2 (4.21) MicroShift versions. These start images are prerequisites for the el98→el98 upgrade CI scenarios added in subsequent commits. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> pre-commit.check-secrets: ENABLED
Test RPM-based upgrade from MicroShift 4.21 (y-2) to 5.0 on RHEL 9.8 using the YMINUS2 release repo and brew RPMs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> pre-commit.check-secrets: ENABLED
…on RHEL 9.8 Test ostree upgrades from MicroShift 4.22 (y-1) and 4.21 (y-2) to 5.0 on RHEL 9.8 with LVMS workload validation and standard1+standard2 suites. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> pre-commit.check-secrets: ENABLED
…n RHEL 9.8 Test bootc upgrades from MicroShift 4.22 (y-1) and 4.21 (y-2) to 5.0 on RHEL 9.8 with LVMS workload validation and standard1+standard2 suites. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> pre-commit.check-secrets: ENABLED
…rry-pick-7381-to-release-5.0 [release-5.0] USHIFT-7518: Support volume group snapshots
…ession) tuned 2.28.0-1.el9fdp regressed the [bootloader] plugin so that, on traditionally-deployed rpm-ostree hosts, the microshift-baseline kernel arguments are no longer persisted to the BLS boot entry (tuned-adm returns 0 but /proc/cmdline is unchanged after reboot). This is a real, shipping defect: the low-latency profile is broken in the field for anyone on tuned 2.28.0, so there is nothing valid to gate PRs on until it is fixed. The composer image cannot be pinned to an older tuned (the edge-commit image-type package set requests tuned unversioned, so a blueprint version pin only produces a depsolve "conflicting requests" error), and downgrading tuned at runtime would only produce a false-green against a version the shipped image does not contain. So the scenario is disabled by renaming it with a .disabled suffix (the harness only runs *.sh scenarios), leaving the test intact for an easy revert. Re-enable by renaming the file back to el98-src@low-latency.sh once the fixed tuned build lands in el9fdp. Tracked by OCPBUGS-123681 (depends on tuned RHEL-261119). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…rry-pick-7376-to-release-5.0 [release-5.0] OCPBUGS-126622: Add startupProbe to ovnk pods
…rry-pick-7384-to-release-5.0 [release-5.0] OCPBUGS-126612: Disable el98 low-latency presubmit (tuned 2.28.0 regression)
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
@redhat-chai-bot: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
WalkthroughWarning Review details and warnings were omitted to fit the comment limit. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: redhat-chai-bot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@redhat-chai-bot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Summary
This is the main-targeted PR based on the rebase branch from PR #7410, with the restricted-v2 metrics CA fix included so standard presubmits can run against
main.The rebase changed the metrics CA volume in kube-state-metrics and node-exporter from the runtime-provided
metrics-client-caConfigMap to anadmin-kubeconfig-signer-cahostPath. The follow-up commit restores the existing ConfigMap contract in the generator and generated manifests so the workloads use/etc/tls/client/client-ca.crt.Fix commit
86fd3721331c097a24104e70d28ce7a8f3abb5cc—NO-ISSUE: restore metrics client CA ConfigMapValidation
bash -nandshellcheckmake verify-shgit diff --checkmake verify-assetswas blocked before asset validation by the workspace Python 3.13 and pinned PyYAML 3.12 incompatibility (collections.Hashable).AI-generated. Review for accuracy.
@pmtk requested via Chai Bot
Summary by CodeRabbit
New Features
v1API support.Bug Fixes
Updates