Skip to content

NO-ISSUE: Update agnhost image to 2.63.0 (mirrored version) - #31498

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
BhargaviGudi:fix-agnhost-image-version
Aug 13, 2026
Merged

NO-ISSUE: Update agnhost image to 2.63.0 (mirrored version)#31498
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
BhargaviGudi:fix-agnhost-image-version

Conversation

@BhargaviGudi

@BhargaviGudi BhargaviGudi commented Aug 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Summary

Fix Additional Storage E2E test to use a mirrored agnhost image version, preventing "unmirrored image" warnings in CI jobs.

Problem

The test was using registry.k8s.io/e2e-test-images/agnhost:2.59 which is no longer in the mirrored images list, causing warnings:

Cluster accessed images that were not mirrored to the testing repository or already part of the cluster,
  see test/extended/util/image/README.md in the openshift/origin repo:
  
  registry.k8s.io/e2e-test-images/agnhost:2.59 from pods:
    namespace/e2e-test-additional-storage-e2e-mr7nl node/ip-10-0-100-216.us-west-2.compute.internal pod/imagestore-fallback-pod
    namespace/e2e-test-additional-storage-e2e-mr7nl node/ip-10-0-100-216.us-west-2.compute.internal pod/imagestore-prepop-pod

Root Cause

commit 9ff6d6990f updated mirrored images during a Kubernetes v1.36.2 bump:

- "registry.k8s.io/e2e-test-images/agnhost:2.59":     2,
+ "registry.k8s.io/e2e-test-images/agnhost:2.63.0":   2,

Changes
File: test/extended/node/additional_storage_e2e.go

  • Changed: agnhost:2.59 → agnhost:2.63.0

Verification

  • agnhost:2.63.0 is in the current mirrored images list (test/extended/util/image/image.go line 53)
  • Test functionality unchanged (only version bump, same image base)
  • No more "unmirrored image" warnings in CI

Testcase ran locally

  ------------------------------
  [Skipped:Disconnected][Skipped:SingleReplicaTopology][apigroup:config.openshift.io][apigroup:machineconfiguration.openshift.io][Jira:Node/CRI-O][sig-node][Feature:AdditionalStorageSupport][OCPFeatureGate:AdditionalStorageConfig][Serial][Disruptive][Suite:openshift/disruptive-longrunning] Additional Storage E2E Tests should verify configuration of all storage types and functionally test image stores
  github.com/openshift/origin/test/extended/node/additional_storage_e2e.go:51
    STEP: Creating a kubernetes client @ 08/12/26 18:07:49.245
  I0812 18:07:54.392225 3741420 client.go:293] configPath is now "/tmp/configfile1994917446"
  I0812 18:07:54.392246 3741420 client.go:368] The user is now "e2e-test-additional-storage-e2e-cbgvd-user"
  I0812 18:07:54.392251 3741420 client.go:373] Creating project "e2e-test-additional-storage-e2e-cbgvd"
  I0812 18:07:55.840983 3741420 client.go:393] Waiting on permissions in project "e2e-test-additional-storage-e2e-cbgvd" ...
  I0812 18:07:57.587641 3741420 client.go:422] DeploymentConfig capability is enabled, adding 'deployer' SA to the list of default SAs
  I0812 18:07:59.977501 3741420 client.go:447] Waiting for ServiceAccount "default" to be provisioned...
  I0812 18:08:01.016416 3741420 client.go:447] Waiting for ServiceAccount "builder" to be provisioned...
  I0812 18:08:01.745953 3741420 client.go:447] Waiting for ServiceAccount "deployer" to be provisioned...
  I0812 18:08:03.096118 3741420 client.go:457] Waiting for RoleBinding "system:image-pullers" to be provisioned...
  I0812 18:08:03.526126 3741420 client.go:457] Waiting for RoleBinding "system:image-builders" to be provisioned...
  I0812 18:08:03.890614 3741420 client.go:457] Waiting for RoleBinding "system:deployers" to be provisioned...
  I0812 18:08:06.094679 3741420 client.go:494] Project "e2e-test-additional-storage-e2e-cbgvd" has been fully provisioned.
  I0812 18:08:06.096155 3741420 framework.go:2330] [precondition-check] checking if cluster is MicroShift
  I0812 18:08:06.497668 3741420 framework.go:2353] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
    STEP: Getting worker node for test @ 08/12/26 18:08:07.633
    STEP: Creating single-node MachineConfigPool for test isolation @ 08/12/26 18:08:08.218
  I0812 18:08:08.728426 3741420 node_mcp_helpers.go:75] Labeling node bgudi-2-n5lpk-worker-a-82p7j with node-role.kubernetes.io/combined-func-test
  I0812 18:08:09.241670 3741420 node_mcp_helpers.go:82] Creating custom MachineConfigPool combined-func-test
  I0812 18:08:09.604953 3741420 node_mcp_helpers.go:121] Waiting for custom MachineConfigPool combined-func-test to be ready
  I0812 18:08:09.605004 3741420 node_utils.go:621] Waiting for MCP combined-func-test to be ready (timeout: 5m0s)...
  I0812 18:08:09.920302 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=false degraded=false renderDegraded=false updated=false machines=0/0
  I0812 18:08:19.992795 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:08:29.934863 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:08:39.960767 3741420 node_utils.go:695] MachineConfigPool combined-func-test is ready: 1/1 machines ready
  I0812 18:08:39.960810 3741420 node_mcp_helpers.go:127] Custom MachineConfigPool combined-func-test created successfully
  I0812 18:08:39.960834 3741420 additional_storage_e2e.go:65] Custom MCP combined-func-test created, targeting node bgudi-2-n5lpk-worker-a-82p7j
    STEP: Phase 1: Creating storage directories and pre-populating test image @ 08/12/26 18:08:39.96
  I0812 18:08:52.259844 3741420 node_utils.go:1025] Node bgudi-2-n5lpk-worker-a-82p7j: directories created: [/var/lib/combined-imagestore /var/lib/combined-artifactstore /var/lib/stargz-store/store]
  I0812 18:08:52.259879 3741420 additional_storage_e2e.go:94] Pre-populating image registry.k8s.io/e2e-test-images/agnhost:2.63.0 to /var/lib/combined-imagestore on node bgudi-2-n5lpk-worker-a-82p7j
  I0812 18:09:05.414633 3741420 additional_storage_e2e.go:102] Image pre-populated successfully: registry.k8s.io/e2e-test-images/agnhost:2.63.0
  I0812 18:09:05.414666 3741420 additional_storage_e2e.go:105] Checking if image exists in primary CRI-O store BEFORE configuring additional stores
  I0812 18:09:09.009542 3741420 additional_storage_e2e.go:115] Verified: image registry.k8s.io/e2e-test-images/agnhost:2.63.0 is NOT in primary CRI-O store (only in /var/lib/combined-imagestore)
    STEP: Phase 2: Creating ContainerRuntimeConfig with all three storage types @ 08/12/26 18:09:09.009
    STEP: Applying ContainerRuntimeConfig and waiting for MCP rollout @ 08/12/26 18:09:09.009
  I0812 18:09:09.009628 3741420 node_kc_cc_helpers.go:111] Creating ContainerRuntimeConfig combined-func-test
  I0812 18:09:09.489284 3741420 node_kc_cc_helpers.go:147] Waiting for MCP combined-func-test to start updating
  I0812 18:09:20.408836 3741420 node_kc_cc_helpers.go:96] MCP combined-func-test has started updating
  I0812 18:09:20.408862 3741420 node_kc_cc_helpers.go:153] Waiting for MCP combined-func-test to complete rollout
  I0812 18:09:20.408872 3741420 node_utils.go:621] Waiting for MCP combined-func-test to be ready (timeout: 15m0s)...
  I0812 18:09:20.911167 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:09:30.877706 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:09:40.744381 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:09:50.891793 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:10:00.857719 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:10:11.017304 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:10:20.900830 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:10:30.755794 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:10:40.792539 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:10:51.017305 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
  I0812 18:11:00.744962 3741420 node_utils.go:695] MachineConfigPool combined-func-test is ready: 1/1 machines ready
    STEP: Phase 3: Verifying storage.conf and CRI-O configuration @ 08/12/26 18:11:00.745
  I0812 18:11:05.376849 3741420 additional_storage_e2e.go:156] Image stores verified in storage.conf
  I0812 18:11:05.376893 3741420 additional_storage_e2e.go:164] Layer stores verified in storage.conf with path /var/lib/stargz-store/store:ref (MCO added :ref)
    STEP: Verifying CRI-O config contains artifact stores @ 08/12/26 18:11:05.376
  I0812 18:11:09.561025 3741420 additional_storage_e2e.go:172] Artifact stores verified in CRI-O config
    STEP: Verifying CRI-O is active with new configuration @ 08/12/26 18:11:09.561
  I0812 18:11:13.569166 3741420 additional_storage_e2e.go:178] CRI-O is active
    STEP: Phase 4: Creating pod using prepopulated image from additional store @ 08/12/26 18:11:13.569
  I0812 18:11:17.261832 3741420 additional_storage_e2e.go:190] Pod using prepopulated image started in 3.692611098s
    STEP: Phase 5: Testing fallback to registry when image removed from additional store @ 08/12/26 18:11:17.261
  I0812 18:11:17.262641 3741420 delete.go:78] Deleting pod "imagestore-prepop-pod" in namespace "e2e-test-additional-storage-e2e-cbgvd"
  I0812 18:11:17.653196 3741420 delete.go:86] Wait up to 5m0s for pod "imagestore-prepop-pod" to be fully deleted
  I0812 18:11:25.344739 3741420 additional_storage_e2e.go:200] Removed image from additional store to test fallback
  I0812 18:11:31.242097 3741420 additional_storage_e2e.go:215] Pod using registry fallback started in 5.897293794s
  I0812 18:11:31.573078 3741420 additional_storage_e2e.go:227] SUCCESS: Image pulled from registry - Successfully pulled image "registry.k8s.io/e2e-test-images/agnhost:2.63.0" in 2.308s (2.308s including waiting). Image size: 164184663 bytes.
  I0812 18:11:31.573132 3741420 additional_storage_e2e.go:234] Phase 5 PASSED: Fallback to registry works when image not in additional store
  I0812 18:11:31.573141 3741420 additional_storage_e2e.go:236] Test PASSED: Configuration verified for all storage types and image stores functionally tested
  I0812 18:11:31.921722 3741420 client.go:731] Deleted {user.openshift.io/v1, Resource=users  e2e-test-additional-storage-e2e-cbgvd-user}, err: <nil>
  I0812 18:11:32.505867 3741420 client.go:731] Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-additional-storage-e2e-cbgvd}, err: <nil>
  I0812 18:11:32.506690 3741420 delete.go:78] Deleting pod "imagestore-fallback-pod" in namespace "e2e-test-additional-storage-e2e-cbgvd"
  I0812 18:11:32.891513 3741420 delete.go:86] Wait up to 5m0s for pod "imagestore-fallback-pod" to be fully deleted
  I0812 18:11:35.738362 3741420 node_kc_cc_helpers.go:121] Cleaning up ContainerRuntimeConfig combined-func-test
  I0812 18:11:36.097608 3741420 node_kc_cc_helpers.go:129] Waiting for MCP combined-func-test to become ready after ContainerRuntimeConfig deletion
  I0812 18:11:36.097649 3741420 node_utils.go:621] Waiting for MCP combined-func-test to be ready (timeout: 15m0s)...
  I0812 18:11:36.421024 3741420 node_utils.go:695] MachineConfigPool combined-func-test is ready: 1/1 machines ready
  I0812 18:11:36.421071 3741420 node_kc_cc_helpers.go:136] ContainerRuntimeConfig combined-func-test cleaned up successfully
  I0812 18:11:36.421084 3741420 node_mcp_helpers.go:140] Removing node label node-role.kubernetes.io/combined-func-test from node bgudi-2-n5lpk-worker-a-82p7j
  I0812 18:11:36.750890 3741420 node_mcp_helpers.go:148] Waiting for node bgudi-2-n5lpk-worker-a-82p7j to transition back to worker pool
  I0812 18:13:17.310997 3741420 node_mcp_helpers.go:167] Deleting custom MachineConfigPool combined-func-test
  I0812 18:13:17.662779 3741420 node_mcp_helpers.go:174] Waiting for worker MCP to stabilize after custom MCP deletion
  I0812 18:13:17.662848 3741420 node_utils.go:621] Waiting for MCP worker to be ready (timeout: 10m0s)...
  I0812 18:13:18.001592 3741420 node_utils.go:695] MachineConfigPool worker is ready: 3/3 machines ready
  I0812 18:13:18.001628 3741420 node_mcp_helpers.go:185] Custom MachineConfigPool combined-func-test cleaned up successfully
    STEP: Destroying namespace "e2e-test-additional-storage-e2e-cbgvd" for this suite. @ 08/12/26 18:13:22.809
  • [333.931 seconds]
  ------------------------------
  [ReportAfterSuite] [sig-testing] Log Check
  k8s.io/kubernetes@v1.36.2/test/e2e/invariants/logcheck/logcheck.go:179
  [ReportAfterSuite] PASSED [0.000 seconds]
  ------------------------------

Summary by CodeRabbit

  • Tests
    • Updated the pre-populated test image used by the additional storage end-to-end test.

@openshift-merge-bot

openshift-merge-bot Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@BhargaviGudi BhargaviGudi changed the title Update agnhost image to 2.63.0 (mirrored version) NO-ISSUE: Update agnhost image to 2.63.0 (mirrored version) Aug 10, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 10, 2026

Copy link
Copy Markdown

@BhargaviGudi: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

Fix Additional Storage E2E test to use a mirrored agnhost image version, preventing "unmirrored image" warnings in CI jobs.

Problem

The test was using registry.k8s.io/e2e-test-images/agnhost:2.59 which is no longer in the mirrored images list, causing warnings:

Cluster accessed images that were not mirrored to the testing repository or already part of the cluster,
 see test/extended/util/image/README.md in the openshift/origin repo:
 
 registry.k8s.io/e2e-test-images/agnhost:2.59 from pods:
   namespace/e2e-test-additional-storage-e2e-mr7nl node/ip-10-0-100-216.us-west-2.compute.internal pod/imagestore-fallback-pod
   namespace/e2e-test-additional-storage-e2e-mr7nl node/ip-10-0-100-216.us-west-2.compute.internal pod/imagestore-prepop-pod

Root Cause

commit 9ff6d6990f updated mirrored images during a Kubernetes v1.36.2 bump:

- "registry.k8s.io/e2e-test-images/agnhost:2.59":     2,
+ "registry.k8s.io/e2e-test-images/agnhost:2.63.0":   2,

Changes
File: test/extended/node/additional_storage_e2e.go

  • Changed: agnhost:2.59 → agnhost:2.63.0

Verification

  • agnhost:2.63.0 is in the current mirrored images list (test/extended/util/image/image.go line 53)
  • Test functionality unchanged (only version bump, same image base)
  • No more "unmirrored image" warnings in CI

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 10, 2026
@openshift-ci
openshift-ci Bot requested review from asahay19 and kannon92 August 10, 2026 06:21
@coderabbitai

coderabbitai Bot commented Aug 10, 2026 •
edited
Loading

Copy link
Copy Markdown

Walkthrough

The additional storage end-to-end test now uses agnhost:2.63.0 instead of agnhost:2.59.

Changes

Additional storage test

Layer / File(s) Summary
Update test image reference
test/extended/node/additional_storage_e2e.go		 The test pre-populates and validates the agnhost:2.63.0 image.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Test Structure And Quality ⚠️ Warning The Ginkgo test has one It covering several storage behaviors and many bare error assertions, such as lines 53, 64, 90, and 233, without diagnostic messages. Split configuration and image-store behaviors into focused It blocks, add meaningful messages to every assertion, and register pod/MCP cleanup before resource creation.
✅ Passed checks (14 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The PR changes only the image reference. The existing Describe and It titles are static literals; dynamic node, pod, and namespace values remain in the test body.
Microshift Test Compatibility ✅ Passed The PR only changes an image tag. The existing test is wrapped in a Describe with unavailable-API apigroup tags, so MicroShift CI skips it.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR changes only the agnhost image tag; no new Ginkgo tests are added, and the existing Describe is labeled [Skipped:SingleReplicaTopology].
Topology-Aware Scheduling Compatibility ✅ Passed The commit changes only the agnhost image tag. It adds no deployment, controller, replica, affinity, topology spread, node selector, or PDB scheduling constraint.
Ote Binary Stdout Contract ✅ Passed The HEAD patch changes only the testImage literal inside a Ginkgo It block; it adds no main, init, suite setup, or process-level stdout writes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The diff only changes an image tag; it adds no Ginkgo test, and the existing suite is marked [Skipped:Disconnected]. The new tag is listed as mirrored.
No-Weak-Crypto ✅ Passed The patch only changes an agnhost image tag; it adds no MD5, SHA-1, DES, RC4, Blowfish, ECB, custom crypto, or secret-comparison logic.
Container-Privileges ✅ Passed The commit only changes the image tag. The pod uses UID 1000 and RunAsNonRoot, drops ALL capabilities, disables privilege escalation, and has no prohibited host or SYS_ADMIN settings.
No-Sensitive-Data-In-Logs ✅ Passed The PR changes only a public agnhost image tag; the parent diff shows no logging changes and no passwords, tokens, PII, or customer data are added.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: updating the agnhost image to mirrored version 2.63.0.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@BhargaviGudi

BhargaviGudi commented Aug 10, 2026

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

@openshift-ci

openshift-ci Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

@BhargaviGudi: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e06702f0-9483-11f1-8cb9-9349733b1961-0

@openshift-ci openshift-ci Bot added the ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review label Aug 10, 2026
@openshift-merge-bot

openshift-merge-bot Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@BhargaviGudi

BhargaviGudi commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

@openshift-ci

openshift-ci Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

@BhargaviGudi: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/11724f40-9537-11f1-8a23-24376f78efef-0

@BhargaviGudi

BhargaviGudi commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-ovn-fips

@BhargaviGudi

BhargaviGudi commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

/payload-job-with-prs periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2 #31498

@openshift-ci

openshift-ci Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

@BhargaviGudi: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/413ff310-9548-11f1-8725-aaaf0f5fcdc6-0

@openshift-ci

openshift-ci Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

@BhargaviGudi: This PR was included in a payload test run from #31498
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-2of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/413ff310-9548-11f1-8725-aaaf0f5fcdc6-0

@BhargaviGudi

BhargaviGudi commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

/payload-job-with-prs periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2 #31498

@openshift-ci

openshift-ci Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

@BhargaviGudi: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

@BhargaviGudi

BhargaviGudi commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2

@openshift-ci

openshift-ci Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

@BhargaviGudi: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-disruptive-longrunning-techpreview-1of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5f3a5880-9569-11f1-9ff7-b6a35ab04e48-0

@BhargaviGudi

BhargaviGudi commented Aug 11, 2026

Copy link
Copy Markdown
Contributor Author

/verified by CI https://pr-payload-tests.ci.openshift.org/runs/ci/5f3a5880-9569-11f1-9ff7-b6a35ab04e48-0

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 11, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 11, 2026

Copy link
Copy Markdown

@BhargaviGudi: This PR has been marked as verified by CI https://pr-payload-tests.ci.openshift.org/runs/ci/5f3a5880-9569-11f1-9ff7-b6a35ab04e48-0.

Details

In response to this:

/verified by CI https://pr-payload-tests.ci.openshift.org/runs/ci/5f3a5880-9569-11f1-9ff7-b6a35ab04e48-0

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.

@coderabbitai coderabbitai Bot mentioned this pull request Aug 11, 2026
Open
@openshift-ci-robot

openshift-ci-robot commented Aug 12, 2026

Copy link
Copy Markdown

@BhargaviGudi: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

Fix Additional Storage E2E test to use a mirrored agnhost image version, preventing "unmirrored image" warnings in CI jobs.

Problem

The test was using registry.k8s.io/e2e-test-images/agnhost:2.59 which is no longer in the mirrored images list, causing warnings:

Cluster accessed images that were not mirrored to the testing repository or already part of the cluster,
 see test/extended/util/image/README.md in the openshift/origin repo:
 
 registry.k8s.io/e2e-test-images/agnhost:2.59 from pods:
   namespace/e2e-test-additional-storage-e2e-mr7nl node/ip-10-0-100-216.us-west-2.compute.internal pod/imagestore-fallback-pod
   namespace/e2e-test-additional-storage-e2e-mr7nl node/ip-10-0-100-216.us-west-2.compute.internal pod/imagestore-prepop-pod

Root Cause

commit 9ff6d6990f updated mirrored images during a Kubernetes v1.36.2 bump:

- "registry.k8s.io/e2e-test-images/agnhost:2.59":     2,
+ "registry.k8s.io/e2e-test-images/agnhost:2.63.0":   2,

Changes
File: test/extended/node/additional_storage_e2e.go

  • Changed: agnhost:2.59 → agnhost:2.63.0

Verification

  • agnhost:2.63.0 is in the current mirrored images list (test/extended/util/image/image.go line 53)
  • Test functionality unchanged (only version bump, same image base)
  • No more "unmirrored image" warnings in CI

Testcase ran locally

 ------------------------------
 [Skipped:Disconnected][Skipped:SingleReplicaTopology][apigroup:config.openshift.io][apigroup:machineconfiguration.openshift.io][Jira:Node/CRI-O][sig-node][Feature:AdditionalStorageSupport][OCPFeatureGate:AdditionalStorageConfig][Serial][Disruptive][Suite:openshift/disruptive-longrunning] Additional Storage E2E Tests should verify configuration of all storage types and functionally test image stores
 github.com/openshift/origin/test/extended/node/additional_storage_e2e.go:51
   STEP: Creating a kubernetes client @ 08/12/26 18:07:49.245
 I0812 18:07:54.392225 3741420 client.go:293] configPath is now "/tmp/configfile1994917446"
 I0812 18:07:54.392246 3741420 client.go:368] The user is now "e2e-test-additional-storage-e2e-cbgvd-user"
 I0812 18:07:54.392251 3741420 client.go:373] Creating project "e2e-test-additional-storage-e2e-cbgvd"
 I0812 18:07:55.840983 3741420 client.go:393] Waiting on permissions in project "e2e-test-additional-storage-e2e-cbgvd" ...
 I0812 18:07:57.587641 3741420 client.go:422] DeploymentConfig capability is enabled, adding 'deployer' SA to the list of default SAs
 I0812 18:07:59.977501 3741420 client.go:447] Waiting for ServiceAccount "default" to be provisioned...
 I0812 18:08:01.016416 3741420 client.go:447] Waiting for ServiceAccount "builder" to be provisioned...
 I0812 18:08:01.745953 3741420 client.go:447] Waiting for ServiceAccount "deployer" to be provisioned...
 I0812 18:08:03.096118 3741420 client.go:457] Waiting for RoleBinding "system:image-pullers" to be provisioned...
 I0812 18:08:03.526126 3741420 client.go:457] Waiting for RoleBinding "system:image-builders" to be provisioned...
 I0812 18:08:03.890614 3741420 client.go:457] Waiting for RoleBinding "system:deployers" to be provisioned...
 I0812 18:08:06.094679 3741420 client.go:494] Project "e2e-test-additional-storage-e2e-cbgvd" has been fully provisioned.
 I0812 18:08:06.096155 3741420 framework.go:2330] [precondition-check] checking if cluster is MicroShift
 I0812 18:08:06.497668 3741420 framework.go:2353] IsMicroShiftCluster: microshift-version configmap not found, not MicroShift
   STEP: Getting worker node for test @ 08/12/26 18:08:07.633
   STEP: Creating single-node MachineConfigPool for test isolation @ 08/12/26 18:08:08.218
 I0812 18:08:08.728426 3741420 node_mcp_helpers.go:75] Labeling node bgudi-2-n5lpk-worker-a-82p7j with node-role.kubernetes.io/combined-func-test
 I0812 18:08:09.241670 3741420 node_mcp_helpers.go:82] Creating custom MachineConfigPool combined-func-test
 I0812 18:08:09.604953 3741420 node_mcp_helpers.go:121] Waiting for custom MachineConfigPool combined-func-test to be ready
 I0812 18:08:09.605004 3741420 node_utils.go:621] Waiting for MCP combined-func-test to be ready (timeout: 5m0s)...
 I0812 18:08:09.920302 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=false degraded=false renderDegraded=false updated=false machines=0/0
 I0812 18:08:19.992795 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:08:29.934863 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:08:39.960767 3741420 node_utils.go:695] MachineConfigPool combined-func-test is ready: 1/1 machines ready
 I0812 18:08:39.960810 3741420 node_mcp_helpers.go:127] Custom MachineConfigPool combined-func-test created successfully
 I0812 18:08:39.960834 3741420 additional_storage_e2e.go:65] Custom MCP combined-func-test created, targeting node bgudi-2-n5lpk-worker-a-82p7j
   STEP: Phase 1: Creating storage directories and pre-populating test image @ 08/12/26 18:08:39.96
 I0812 18:08:52.259844 3741420 node_utils.go:1025] Node bgudi-2-n5lpk-worker-a-82p7j: directories created: [/var/lib/combined-imagestore /var/lib/combined-artifactstore /var/lib/stargz-store/store]
 I0812 18:08:52.259879 3741420 additional_storage_e2e.go:94] Pre-populating image registry.k8s.io/e2e-test-images/agnhost:2.63.0 to /var/lib/combined-imagestore on node bgudi-2-n5lpk-worker-a-82p7j
 I0812 18:09:05.414633 3741420 additional_storage_e2e.go:102] Image pre-populated successfully: registry.k8s.io/e2e-test-images/agnhost:2.63.0
 I0812 18:09:05.414666 3741420 additional_storage_e2e.go:105] Checking if image exists in primary CRI-O store BEFORE configuring additional stores
 I0812 18:09:09.009542 3741420 additional_storage_e2e.go:115] Verified: image registry.k8s.io/e2e-test-images/agnhost:2.63.0 is NOT in primary CRI-O store (only in /var/lib/combined-imagestore)
   STEP: Phase 2: Creating ContainerRuntimeConfig with all three storage types @ 08/12/26 18:09:09.009
   STEP: Applying ContainerRuntimeConfig and waiting for MCP rollout @ 08/12/26 18:09:09.009
 I0812 18:09:09.009628 3741420 node_kc_cc_helpers.go:111] Creating ContainerRuntimeConfig combined-func-test
 I0812 18:09:09.489284 3741420 node_kc_cc_helpers.go:147] Waiting for MCP combined-func-test to start updating
 I0812 18:09:20.408836 3741420 node_kc_cc_helpers.go:96] MCP combined-func-test has started updating
 I0812 18:09:20.408862 3741420 node_kc_cc_helpers.go:153] Waiting for MCP combined-func-test to complete rollout
 I0812 18:09:20.408872 3741420 node_utils.go:621] Waiting for MCP combined-func-test to be ready (timeout: 15m0s)...
 I0812 18:09:20.911167 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:09:30.877706 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:09:40.744381 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:09:50.891793 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:10:00.857719 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:10:11.017304 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:10:20.900830 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:10:30.755794 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:10:40.792539 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:10:51.017305 3741420 node_utils.go:698] MachineConfigPool combined-func-test not ready yet: updating=true degraded=false renderDegraded=false updated=false machines=0/1
 I0812 18:11:00.744962 3741420 node_utils.go:695] MachineConfigPool combined-func-test is ready: 1/1 machines ready
   STEP: Phase 3: Verifying storage.conf and CRI-O configuration @ 08/12/26 18:11:00.745
 I0812 18:11:05.376849 3741420 additional_storage_e2e.go:156] Image stores verified in storage.conf
 I0812 18:11:05.376893 3741420 additional_storage_e2e.go:164] Layer stores verified in storage.conf with path /var/lib/stargz-store/store:ref (MCO added :ref)
   STEP: Verifying CRI-O config contains artifact stores @ 08/12/26 18:11:05.376
 I0812 18:11:09.561025 3741420 additional_storage_e2e.go:172] Artifact stores verified in CRI-O config
   STEP: Verifying CRI-O is active with new configuration @ 08/12/26 18:11:09.561
 I0812 18:11:13.569166 3741420 additional_storage_e2e.go:178] CRI-O is active
   STEP: Phase 4: Creating pod using prepopulated image from additional store @ 08/12/26 18:11:13.569
 I0812 18:11:17.261832 3741420 additional_storage_e2e.go:190] Pod using prepopulated image started in 3.692611098s
   STEP: Phase 5: Testing fallback to registry when image removed from additional store @ 08/12/26 18:11:17.261
 I0812 18:11:17.262641 3741420 delete.go:78] Deleting pod "imagestore-prepop-pod" in namespace "e2e-test-additional-storage-e2e-cbgvd"
 I0812 18:11:17.653196 3741420 delete.go:86] Wait up to 5m0s for pod "imagestore-prepop-pod" to be fully deleted
 I0812 18:11:25.344739 3741420 additional_storage_e2e.go:200] Removed image from additional store to test fallback
 I0812 18:11:31.242097 3741420 additional_storage_e2e.go:215] Pod using registry fallback started in 5.897293794s
 I0812 18:11:31.573078 3741420 additional_storage_e2e.go:227] SUCCESS: Image pulled from registry - Successfully pulled image "registry.k8s.io/e2e-test-images/agnhost:2.63.0" in 2.308s (2.308s including waiting). Image size: 164184663 bytes.
 I0812 18:11:31.573132 3741420 additional_storage_e2e.go:234] Phase 5 PASSED: Fallback to registry works when image not in additional store
 I0812 18:11:31.573141 3741420 additional_storage_e2e.go:236] Test PASSED: Configuration verified for all storage types and image stores functionally tested
 I0812 18:11:31.921722 3741420 client.go:731] Deleted {user.openshift.io/v1, Resource=users  e2e-test-additional-storage-e2e-cbgvd-user}, err: <nil>
 I0812 18:11:32.505867 3741420 client.go:731] Deleted {oauth.openshift.io/v1, Resource=oauthclients  e2e-client-e2e-test-additional-storage-e2e-cbgvd}, err: <nil>
 I0812 18:11:32.506690 3741420 delete.go:78] Deleting pod "imagestore-fallback-pod" in namespace "e2e-test-additional-storage-e2e-cbgvd"
 I0812 18:11:32.891513 3741420 delete.go:86] Wait up to 5m0s for pod "imagestore-fallback-pod" to be fully deleted
 I0812 18:11:35.738362 3741420 node_kc_cc_helpers.go:121] Cleaning up ContainerRuntimeConfig combined-func-test
 I0812 18:11:36.097608 3741420 node_kc_cc_helpers.go:129] Waiting for MCP combined-func-test to become ready after ContainerRuntimeConfig deletion
 I0812 18:11:36.097649 3741420 node_utils.go:621] Waiting for MCP combined-func-test to be ready (timeout: 15m0s)...
 I0812 18:11:36.421024 3741420 node_utils.go:695] MachineConfigPool combined-func-test is ready: 1/1 machines ready
 I0812 18:11:36.421071 3741420 node_kc_cc_helpers.go:136] ContainerRuntimeConfig combined-func-test cleaned up successfully
 I0812 18:11:36.421084 3741420 node_mcp_helpers.go:140] Removing node label node-role.kubernetes.io/combined-func-test from node bgudi-2-n5lpk-worker-a-82p7j
 I0812 18:11:36.750890 3741420 node_mcp_helpers.go:148] Waiting for node bgudi-2-n5lpk-worker-a-82p7j to transition back to worker pool
 I0812 18:13:17.310997 3741420 node_mcp_helpers.go:167] Deleting custom MachineConfigPool combined-func-test
 I0812 18:13:17.662779 3741420 node_mcp_helpers.go:174] Waiting for worker MCP to stabilize after custom MCP deletion
 I0812 18:13:17.662848 3741420 node_utils.go:621] Waiting for MCP worker to be ready (timeout: 10m0s)...
 I0812 18:13:18.001592 3741420 node_utils.go:695] MachineConfigPool worker is ready: 3/3 machines ready
 I0812 18:13:18.001628 3741420 node_mcp_helpers.go:185] Custom MachineConfigPool combined-func-test cleaned up successfully
   STEP: Destroying namespace "e2e-test-additional-storage-e2e-cbgvd" for this suite. @ 08/12/26 18:13:22.809
 • [333.931 seconds]
 ------------------------------
 [ReportAfterSuite] [sig-testing] Log Check
 k8s.io/kubernetes@v1.36.2/test/e2e/invariants/logcheck/logcheck.go:179
 [ReportAfterSuite] PASSED [0.000 seconds]
 ------------------------------

Summary by CodeRabbit

  • Tests
  • Updated the pre-populated test image used by the additional storage end-to-end test.

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.

@asahay19

asahay19 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 12, 2026
@haircommander

haircommander commented Aug 13, 2026

Copy link
Copy Markdown
Member

/approve

@openshift-ci

openshift-ci Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asahay19, BhargaviGudi, haircommander

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 13, 2026
@openshift-merge-bot

openshift-merge-bot Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@openshift-merge-bot
openshift-merge-bot Bot merged commit 35d5c1a into openshift:main Aug 13, 2026
10 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] approved these changes
@asahay19 asahay19 Awaiting requested review from asahay19
@kannon92 kannon92 Awaiting requested review from kannon92
+1 more reviewer
@haircommander haircommander haircommander approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

@haircommander haircommander

@asahay19 asahay19

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@BhargaviGudi @openshift-ci-robot @asahay19 @haircommander