[release-5.0] OCPBUGS-111891: Add proxy env vars to cluster-storage-operator deployment by openshift-cherrypick-robot · Pull Request #9332 · openshift/hypershift

openshift-cherrypick-robot · 2026-08-18T12:48:07Z

This is an automated cherry-pick of #9256

/assign openshift-ci-robot

…eployment The CSO deployment was missing HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables when the management cluster is configured with a proxy. This caused downstream CSI driver operators to fail reaching AWS APIs, breaking all PVC provisioning on proxy-required management clusters.

openshift-merge-bot · 2026-08-18T12:48:10Z

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: LGTM mode

openshift-ci-robot · 2026-08-18T12:48:11Z

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-105282 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-5.0] OCPBUGS-111891: Add proxy env vars to cluster-storage-operator deployment

Details

In response to this:

This is an automated cherry-pick of #9256

/assign openshift-ci-robot

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 · 2026-08-18T12:48:19Z

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 67d5dd74-d547-47c4-882d-0db8edcf4850

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

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

openshift-ci-robot · 2026-08-18T12:48:39Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-111891, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-105282 to target a version in 5.1.0, but it targets "5.0" instead

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:

This is an automated cherry-pick of #9256

/assign openshift-ci-robot

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-bot · 2026-08-19T17:32:22Z

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aks
/test e2e-aws
/test e2e-aws-upgrade-hypershift-operator
/test e2e-azure-aks-external-oidc
/test e2e-kubevirt-aws-ovn-reduced
/test e2e-v2-aws
/test e2e-v2-azure-self-managed
/test e2e-v2-gke

openshift-ci · 2026-08-19T17:32:28Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: csrwng, openshift-cherrypick-robot

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~~ [csrwng]

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

PoornimaSingour · 2026-08-20T04:27:34Z

/retest

vsolanki12 · 2026-08-20T06:50:58Z

/verified by @vsolanki

Test result:
Step 1: CPO sets proxy on CSO

    $ oc get deployment cluster-storage-operator -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
    Container: cluster-storage-operator
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost

Step 2: CSO sets proxy on aws-ebs-csi-driver-operator

    $ oc get deployment aws-ebs-csi-driver-operator -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
    Container: aws-ebs-csi-driver-operator
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost
    Container: token-minter
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost

Step 3: aws-ebs-csi-driver-operator sets proxy on aws-ebs-csi-driver-controller (all 12 containers)

  $ oc get deployment aws-ebs-csi-driver-controller -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
    Container: csi-driver
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128

    Container: csi-provisioner
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: csi-attacher
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: csi-resizer
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: csi-snapshotter
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: csi-liveness-probe
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    Container: token-minter
      HTTP_PROXY=http://<PROXY_IP>:3128
      HTTPS_PROXY=http://<PROXY_IP>:3128
      NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

    (+ 5 kube-rbac-proxy sidecar containers, all with same proxy vars)

  PVC Provisioning Test (end-to-end proof)
  Guest cluster nodes
    $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get nodes
    NAME                          STATUS   ROLES    AGE   VERSION
    ip-10-0-128-46.ec2.internal   Ready    worker   10m   v1.35.3
    ip-10-0-133-12.ec2.internal   Ready    worker   10m   v1.35.3

    PVC status — Bound
    $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pvc -n default
    NAME             STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
    proxy-test-pvc   Bound    pvc-c3bd0113-9f67-4a2b-be7d-07a3b323c869   1Gi        RWO            gp3-csi        48m

  PV details — gp3 EBS volume provisioned
   $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pv
   NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM
   STORAGECLASS   AGE
   pvc-c3bd0113-9f67-4a2b-be7d-07a3b323c869   1Gi        RWO            Delete           Bound    default/proxy-test-pvc
   gp3-csi        8m56s

  Pod status — Running
    $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pod proxy-test-pod -n default
    NAME             READY   STATUS    RESTARTS   AGE
    proxy-test-pod   1/1     Running   0          48m

This proves aws-ebs-csi-driver-controller now reach AWS STS through proxy, assume IAM role, call EC2 CreateVolume ok.

openshift-ci-robot · 2026-08-20T06:51:09Z

@vsolanki12: This PR has been marked as verified by @vsolanki.

Details

In response to this:

/verified by @vsolanki

Test result:
Step 1: CPO sets proxy on CSO

   $ oc get deployment cluster-storage-operator -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
   Container: cluster-storage-operator
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost

Step 2: CSO sets proxy on aws-ebs-csi-driver-operator

   $ oc get deployment aws-ebs-csi-driver-operator -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
   Container: aws-ebs-csi-driver-operator
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost
   Container: token-minter
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy-mgmt.india.aws.cee.support,kube-apiserver,localhost

Step 3: aws-ebs-csi-driver-operator sets proxy on aws-ebs-csi-driver-controller (all 12 containers)

 $ oc get deployment aws-ebs-csi-driver-controller -n local-cluster-proxy-test-full -o json | grep -A1 PROXY
   Container: csi-driver
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128

   Container: csi-provisioner
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: csi-attacher
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: csi-resizer
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: csi-snapshotter
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: csi-liveness-probe
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   Container: token-minter
     HTTP_PROXY=http://<PROXY_IP>:3128
     HTTPS_PROXY=http://<PROXY_IP>:3128
     NO_PROXY=.cluster.local,.ec2.internal,.svc,10.0.0.0/16,10.128.0.0/14,...

   (+ 5 kube-rbac-proxy sidecar containers, all with same proxy vars)

 PVC Provisioning Test (end-to-end proof)
 Guest cluster nodes
   $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get nodes
   NAME                          STATUS   ROLES    AGE   VERSION
   ip-10-0-128-46.ec2.internal   Ready    worker   10m   v1.35.3
   ip-10-0-133-12.ec2.internal   Ready    worker   10m   v1.35.3

   PVC status — Bound
   $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pvc -n default
   NAME             STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
   proxy-test-pvc   Bound    pvc-c3bd0113-9f67-4a2b-be7d-07a3b323c869   1Gi        RWO            gp3-csi        48m

 PV details — gp3 EBS volume provisioned
  $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pv
  NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM
  STORAGECLASS   AGE
  pvc-c3bd0113-9f67-4a2b-be7d-07a3b323c869   1Gi        RWO            Delete           Bound    default/proxy-test-pvc
  gp3-csi        8m56s

 Pod status — Running
   $ oc --kubeconfig=/tmp/guest-kubeconfig.yaml get pod proxy-test-pod -n default
   NAME             READY   STATUS    RESTARTS   AGE
   proxy-test-pod   1/1     Running   0          48m

This proves aws-ebs-csi-driver-controller now reach AWS STS through proxy, assume IAM role, call EC2 CreateVolume ok.

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.

PoornimaSingour · 2026-08-20T10:40:08Z

/retest

PoornimaSingour · 2026-08-20T16:40:47Z

/retest

PoornimaSingour · 2026-08-21T04:21:58Z

/retest

PoornimaSingour · 2026-08-25T05:18:18Z

/retest

PoornimaSingour · 2026-08-27T06:30:28Z

/retest

PoornimaSingour · 2026-08-30T16:43:59Z

/retest

PoornimaSingour · 2026-08-31T17:50:24Z

/retest

PoornimaSingour · 2026-08-31T18:18:50Z

e2e-kubevirt-aws-ovn-reduced job is not passing due to infra issue:

Evidence of Systemic Issue

I checked other recent PRs targeting release-5.0:

PR 9452: e2e-kubevirt-aws-ovn-reduced - PENDING (no execution link)
PR 9430: e2e-kubevirt-aws-ovn-reduced - FAILURE
PR 9408: e2e-kubevirt-aws-ovn-reduced - FAILURE
PR 9332 (mine): e2e-kubevirt-aws-ovn-reduced - Failure

All other tests on PR #9332 are passing, including:

e2e-aws ✓
e2e-v2-aws ✓
e2e-aks ✓
e2e-azure-aks-external-oidc ✓
e2e-v2-azure-self-managed ✓
e2e-v2-gke ✓
e2e-aws-upgrade-hypershift-operator ✓

Comparison with Original PR

The original PR #9256 (targeting main branch) had the same test pass successfully (pull-ci-openshift-hypershift-main-e2e-kubevirt-aws-ovn-reduced).

Key Failure looks like an infra issue:
Failed to wait for 2 nodes to become ready in 45m0s: context deadline exceeded
observed **v1.Node collection invalid: expected 2 nodes, got 1

Tests that failed:

TestCreateCluster - only got 1 worker node instead of 2
TestAutoscaling - cluster operators didn't become available in time

jparrill · 2026-09-01T08:50:07Z

/retest-required

jparrill · 2026-09-01T08:50:56Z

/jira refresh

openshift-ci-robot · 2026-09-01T08:51:00Z

@jparrill: This pull request references Jira Issue OCPBUGS-111891, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
expected dependent Jira Issue OCPBUGS-105282 to target a version in 5.1.0, but it targets "5.0" instead

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.

jparrill · 2026-09-01T08:55:03Z

/jira refresh

openshift-ci-robot · 2026-09-01T08:55:09Z

@jparrill: This pull request references Jira Issue OCPBUGS-111891, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-105282 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-105282 targets the "5.1" version, which is one of the valid target versions: 5.1.0
bug has dependents

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.

jparrill · 2026-09-01T08:55:28Z

/label backport-risk-assessed

openshift-ci · 2026-09-01T08:55:58Z

@jparrill: The label(s) backport-risk-assessed cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-staff-engineers, openshift-release-oversight, openshift-sustaining-engineers

Details

In response to this:

/label backport-risk-assessed

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.

csrwng · 2026-09-01T13:41:00Z

/label backport-risk-assessed

openshift-merge-bot · 2026-09-01T14:25:00Z

/retest-required

Remaining retests: 0 against base HEAD c94b15c and 2 for PR HEAD 381fabd in total

PoornimaSingour · 2026-09-02T06:44:46Z

/retest

csrwng · 2026-09-02T14:25:52Z

/override ci/prow/e2e-kubevirt-aws-ovn-reduced
The failures are not related to this PR. They are caused by VMs failing to be created.

openshift-ci · 2026-09-02T14:26:23Z

@csrwng: Overrode contexts on behalf of csrwng: ci/prow/e2e-kubevirt-aws-ovn-reduced

Details

In response to this:

/override ci/prow/e2e-kubevirt-aws-ovn-reduced
The failures are not related to this PR. They are caused by VMs failing to be created.

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.

openshift-merge-bot · 2026-09-02T16:58:38Z

/retest-required

Remaining retests: 0 against base HEAD 93850b7 and 1 for PR HEAD 381fabd in total

openshift-ci-robot · 2026-09-02T18:08:11Z

@openshift-cherrypick-robot: Jira Issue Verification Checks: Jira Issue OCPBUGS-111891
✔️ 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-111891 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:

This is an automated cherry-pick of #9256

/assign openshift-ci-robot

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 · 2026-09-02T18:22:41Z

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-kubevirt-aws-ovn-reduced	`381fabd`	link	true	`/test e2e-kubevirt-aws-ovn-reduced`

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.

PoornimaSingour · 2026-09-03T02:50:47Z

/jira backport release-4.22

openshift-ci-robot · 2026-09-03T02:51:57Z

@PoornimaSingour: The following backport issues have been created:

Jira Issue OCPBUGS-119698 for branch release-4.22

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22

Details

In response to this:

/jira backport release-4.22

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-cherrypick-robot · 2026-09-03T02:53:13Z

@openshift-ci-robot: #9332 failed to apply on top of branch "release-4.22":

Applying: fix(OCPBUGS-105282): Add proxy env vars to cluster-storage-operator deployment
Using index info to reconstruct a base tree...
M	control-plane-operator/controllers/hostedcontrolplane/v2/storage/deployment.go
Falling back to patching base and 3-way merge...
Auto-merging control-plane-operator/controllers/hostedcontrolplane/v2/storage/deployment.go
CONFLICT (content): Merge conflict in control-plane-operator/controllers/hostedcontrolplane/v2/storage/deployment.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 fix(OCPBUGS-105282): Add proxy env vars to cluster-storage-operator deployment

Details

In response to this:

@PoornimaSingour: The following backport issues have been created:

Jira Issue OCPBUGS-119698 for branch release-4.22

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22

In response to this:

/jira backport release-4.22

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.

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.

openshift-cherrypick-robot assigned openshift-ci-robot Aug 18, 2026

openshift-cherrypick-robot mentioned this pull request Aug 18, 2026

OCPBUGS-105282: Add proxy env vars to cluster-storage-operator deployment #9256

Merged

8 tasks

openshift-ci Bot added the do-not-merge/needs-area label Aug 18, 2026

openshift-ci Bot changed the title ~~[release-5.0] OCPBUGS-105282: Add proxy env vars to cluster-storage-operator deployment~~ [release-5.0] OCPBUGS-111891: Add proxy env vars to cluster-storage-operator deployment Aug 18, 2026

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 18, 2026

openshift-ci Bot requested review from Nirshal and ironcladlou August 18, 2026 12:51

openshift-ci Bot added area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release and removed do-not-merge/needs-area labels Aug 18, 2026

csrwng approved these changes Aug 19, 2026

View reviewed changes

openshift-ci Bot assigned csrwng Aug 19, 2026

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

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

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

PoornimaSingour mentioned this pull request Aug 31, 2026

OCPBUGS-86963: fix blackholenetwork region resolution for HyperShift workflows openshift/release#80204

Open

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 1, 2026

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 1, 2026

openshift-merge-bot Bot merged commit 7a51709 into openshift:release-5.0 Sep 2, 2026
25 checks passed

Uh oh!

Conversation

openshift-cherrypick-robot commented Aug 18, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 18, 2026

Uh oh!

openshift-ci-robot commented Aug 18, 2026

Uh oh!

coderabbitai Bot commented Aug 18, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Aug 18, 2026

Uh oh!

openshift-merge-bot Bot commented Aug 19, 2026

Uh oh!

openshift-ci Bot commented Aug 19, 2026

Uh oh!

PoornimaSingour commented Aug 20, 2026

Uh oh!

vsolanki12 commented Aug 20, 2026

Uh oh!

openshift-ci-robot commented Aug 20, 2026

Uh oh!

PoornimaSingour commented Aug 20, 2026

Uh oh!

PoornimaSingour commented Aug 20, 2026

Uh oh!

PoornimaSingour commented Aug 21, 2026

Uh oh!

PoornimaSingour commented Aug 25, 2026

Uh oh!

PoornimaSingour commented Aug 27, 2026

Uh oh!

PoornimaSingour commented Aug 30, 2026

Uh oh!

PoornimaSingour commented Aug 31, 2026

Uh oh!

PoornimaSingour commented Aug 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jparrill commented Sep 1, 2026

Uh oh!

jparrill commented Sep 1, 2026

Uh oh!

openshift-ci-robot commented Sep 1, 2026

Uh oh!

jparrill commented Sep 1, 2026

Uh oh!

openshift-ci-robot commented Sep 1, 2026

Uh oh!

jparrill commented Sep 1, 2026

Uh oh!

openshift-ci Bot commented Sep 1, 2026

Uh oh!

csrwng commented Sep 1, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 1, 2026

Uh oh!

PoornimaSingour commented Sep 2, 2026

Uh oh!

csrwng commented Sep 2, 2026

Uh oh!

openshift-ci Bot commented Sep 2, 2026

Uh oh!

openshift-merge-bot Bot commented Sep 2, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Sep 2, 2026

Uh oh!

openshift-ci Bot commented Sep 2, 2026

Uh oh!

PoornimaSingour commented Sep 3, 2026

Uh oh!

openshift-ci-robot commented Sep 3, 2026

Uh oh!

openshift-cherrypick-robot commented Sep 3, 2026

Uh oh!

Reviewers

Assignees

Labels

PoornimaSingour commented Aug 31, 2026 •

edited

Loading