OCPBUGS-67012: volume-data-source-validator must use IfNotPresent image pull policy

[RomanBednar]

Changes the volume-data-source-validator deployment to use imagePullPolicy: IfNotPresent instead of Always. This prevents the pod from failing with ImagePullBackOff in disconnected environments. As a result, the storage cluster operator no longer becomes degraded due to this issue.

cc @openshift/storage

[openshift-ci-robot]

@RomanBednar: This pull request references Jira Issue OCPBUGS-67012, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Changes the volume-data-source-validator deployment to use imagePullPolicy: IfNotPresent instead of Always. This prevents the pod from failing with ImagePullBackOff in disconnected environments. As a result, the storage cluster operator no longer becomes degraded due to this issue.

cc @openshift/storage

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RomanBednar

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:

• OWNERS [RomanBednar]

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

[mpatlasov]

/lgtm
/test hypershift-e2e-aks

[openshift-ci]

@RomanBednar: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

[duanwei33]

The volume-data-source-validator's imagePullPolicy changes to IfNotPresent now:

$ curl -s "https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_cluster-storage-operator/650/pull-ci-openshift-cluster-storage-operator-main-e2e-aws-csi/1999405541872373760/artifacts/e2e-aws-csi/gather-extra/artifacts/pods.json" | jq -r '.items[] | select(.metadata.name | contains("volume-data-source-validator")) | .spec.containers[] | select(.name == "volume-data-source-validator") | .imagePullPolicy'
IfNotPresent

[duanwei33]

/verified by manual check in #650 (comment)

[openshift-ci-robot]

@duanwei33: This PR has been marked as verified by manual check in https://github.com/openshift/cluster-storage-operator/pull/650#issuecomment-3652607008.

Details

In response to this:

/verified by manual check in #650 (comment)

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.

[duanwei33]

/jira refresh

[openshift-ci-robot]

@duanwei33: This pull request references Jira Issue OCPBUGS-67012, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

[duanwei33]

/jira refresh

[openshift-ci-robot]

@duanwei33: This pull request references Jira Issue OCPBUGS-67012, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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.

[jsafrane]

/label acknowledge-critical-fixes-only
Storage does not work in disconnected clusters.

[openshift-ci-robot]

@RomanBednar: Jira Issue Verification Checks: Jira Issue OCPBUGS-67012
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-67012 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Changes the volume-data-source-validator deployment to use imagePullPolicy: IfNotPresent instead of Always. This prevents the pod from failing with ImagePullBackOff in disconnected environments. As a result, the storage cluster operator no longer becomes degraded due to this issue.

cc @openshift/storage

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-merge-robot]

Fix included in accepted release 4.22.0-0.nightly-2025-12-17-101159

[RomanBednar]

/cherry-pick release-4.21

[openshift-cherrypick-robot]

@RomanBednar: new pull request created: #652

Details

In response to this:

/cherry-pick release-4.21

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 kubernetes-sigs/prow repository.