Skip to content

OCPBUGS-99490: Apply some static assets earlier, before starting controllers#584

Open
mpatlasov wants to merge 1 commit into
openshift:mainfrom
mpatlasov:OCPBUGS-99490-Apply-Prerequisite-Assets
Open

OCPBUGS-99490: Apply some static assets earlier, before starting controllers#584
mpatlasov wants to merge 1 commit into
openshift:mainfrom
mpatlasov:OCPBUGS-99490-Apply-Prerequisite-Assets

Conversation

@mpatlasov

Copy link
Copy Markdown
Contributor

https://redhat.atlassian.net/browse/OCPBUGS-99490

CSIControllerSet.Run() starts all controllers as parallel goroutines with no ordering guarantee. The Deployment controller can create pods before StaticResourcesController applies the assets for ClusterRole and ClusterRoleBinding, causing SCC admission to deny pod creation.

Such race-condition leads to events like:

  message: 'Error creating: pods "gcp-pd-csi-driver-controller-6d9b8c6584-" is forbidden:
    unable to validate against any security context constraint: provider "hostnetwork-v2":
    Forbidden: not usable by user or serviceaccount'

The commit fixes the issue by applying all assets defined in OperatorConfig.PrerequisiteAssets before controllers start.

@openshift-merge-bot

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

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@mpatlasov: This pull request references Jira Issue OCPBUGS-99490, which is valid.

3 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)

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

Details

In response to this:

https://redhat.atlassian.net/browse/OCPBUGS-99490

CSIControllerSet.Run() starts all controllers as parallel goroutines with no ordering guarantee. The Deployment controller can create pods before StaticResourcesController applies the assets for ClusterRole and ClusterRoleBinding, causing SCC admission to deny pod creation.

Such race-condition leads to events like:

 message: 'Error creating: pods "gcp-pd-csi-driver-controller-6d9b8c6584-" is forbidden:
   unable to validate against any security context constraint: provider "hostnetwork-v2":
   Forbidden: not usable by user or serviceaccount'

The commit fixes the issue by applying all assets defined in OperatorConfig.PrerequisiteAssets before controllers start.

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-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jul 24, 2026
@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: fa24f093-50e4-4490-aba3-2ba5a5de17f9

📥 Commits

Reviewing files that changed from the base of the PR and between 67852d3 and d6b5c3b.

📒 Files selected for processing (5)
  • pkg/driver/gcp-pd/gcp_pd.go
  • pkg/operator/config/config.go
  • pkg/operator/prerequisites.go
  • pkg/operator/prerequisites_test.go
  • pkg/operator/starter.go
🚧 Files skipped from review as they are similar to previous changes (4)
  • pkg/operator/starter.go
  • pkg/operator/config/config.go
  • pkg/operator/prerequisites.go
  • pkg/operator/prerequisites_test.go

📝 Walkthrough

Walkthrough

The operator configuration now declares prerequisite asset filenames, with the GCP PD driver providing service account and RBAC assets. A new helper applies these files with retries, error aggregation, logging, delays, and context cancellation. RunOperator invokes it after informer synchronization and before controller startup, returning errors immediately. Tests cover successful application, invalid inputs, transient failures, retries, and ServiceAccount creation.

Suggested reviewers: dobsonj, romanbednar

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: applying static assets before controllers start.
Description check ✅ Passed The description directly matches the change by explaining the race condition and the prerequisite asset fix.
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 PASS: The new test file uses fixed t.Run names, and no added test titles interpolate pod names, timestamps, UUIDs, nodes, or namespaces.
Test Structure And Quality ✅ Passed No Ginkgo tests were changed; the new table-driven unit test uses isolated fake clients, restores globals, and includes clear failure messages.
Microshift Test Compatibility ✅ Passed No new Ginkgo e2e specs were added; the only test is a standard Go unit test, so MicroShift-specific gating is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No new Ginkgo e2e tests were added; the only new test is a unit test using fake clients, so there are no SNO-specific cluster assumptions to review.
Topology-Aware Scheduling Compatibility ✅ Passed The PR only adds prerequisite asset application plumbing; it introduces no new nodeSelector, affinity, replica, or topology-based scheduling assumptions.
Ote Binary Stdout Contract ✅ Passed No stdout writes were added in the touched startup paths; new code only uses klog logging, and no fmt.Print/log-to-stdout calls were found.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The only new test is a plain Go unit test, not Ginkgo e2e, and it uses fake clients with no IPv4 or external-network assumptions.
No-Weak-Crypto ✅ Passed Touched files only add prerequisite-asset wiring; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons found.
Container-Privileges ✅ Passed Diff only adds prereq asset wiring; no changed K8s manifests add privileged/hostNetwork/hostPID/hostIPC/SYS_ADMIN/allowPrivilegeEscalation.
No-Sensitive-Data-In-Logs ✅ Passed New logs only report prerequisite asset filenames, statuses, and wrapped apply errors; no secrets, PII, API keys, or internal hostnames are logged in the changed code.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci
openshift-ci Bot requested review from RomanBednar and dobsonj July 24, 2026 03:19
@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpatlasov

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 Jul 24, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@pkg/operator/prerequisites_test.go`:
- Line 110: Update the test setup at the fake clientset initialization to
replace the deprecated fakecore.NewSimpleClientset() constructor with
fakecore.NewClientset(), preserving the existing client behavior.

In `@pkg/operator/prerequisites.go`:
- Around line 61-63: Replace the unconditional time.Sleep retry backoff in the
prerequisite retry flow with a context-aware timer/select using the existing
context.Context, returning promptly when cancellation or timeout occurs while
preserving the delay before the next attempt when the context remains active.

In `@pkg/operator/starter.go`:
- Around line 271-274: Move the applyPrerequisites call in starterController
before the Precondition branch so it executes for both startup paths, including
configurations that define both Precondition and PrerequisiteAssets. Preserve
the existing error propagation and asset arguments.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 2bf677af-2bd8-48cd-bd79-16b1fca0b40d

📥 Commits

Reviewing files that changed from the base of the PR and between 1da4798 and 67852d3.

📒 Files selected for processing (5)
  • pkg/driver/gcp-pd/gcp_pd.go
  • pkg/operator/config/config.go
  • pkg/operator/prerequisites.go
  • pkg/operator/prerequisites_test.go
  • pkg/operator/starter.go

Comment thread pkg/operator/prerequisites_test.go Outdated
Comment thread pkg/operator/prerequisites.go
Comment thread pkg/operator/starter.go Outdated
@mpatlasov

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bdd1d2a0-870f-11f1-8d71-c8ea5723ebf9-0

@mpatlasov

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

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

  • periodic-ci-openshift-release-main-ci-5.0-e2e-gcp-ovn-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9f1e9cb0-876b-11f1-91ae-bccd9c78cad4-0

CSIControllerSet.Run() starts all controllers as parallel goroutines with no ordering guarantee.
The Deployment controller can create pods before StaticResourcesController applies the assets for ClusterRole and ClusterRoleBinding, causing SCC admission to deny pod creation.

Such race-condition leads to events like:
```
  message: 'Error creating: pods "gcp-pd-csi-driver-controller-6d9b8c6584-" is forbidden:
    unable to validate against any security context constraint: provider "hostnetwork-v2":
    Forbidden: not usable by user or serviceaccount'
```

The commit fixes the issue by applying all assets defined in OperatorConfig.PrerequisiteAssets before controllers start.
@mpatlasov
mpatlasov force-pushed the OCPBUGS-99490-Apply-Prerequisite-Assets branch from 67852d3 to d6b5c3b Compare July 24, 2026 17:59
@mpatlasov

Copy link
Copy Markdown
Contributor Author

Last force-push fixed three suggestions from @coderabbitai:

  • s/fakecore.NewSimpleClientset()/fakecore.NewClientset()
  • Move applyPrerequisites() call before Precondition check
  • Use ctx for delay between iterations in prerequisite loop

@coderabbitai

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown

Tip

For best results, initiate chat on the files or code changes.

@mpatlasov Thanks for addressing all three suggestions in the force-push. The prerequisite setup and retry behavior now align with the intended controller startup ordering and cancellation handling.

@dobsonj

dobsonj commented Jul 24, 2026

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-upgrade
/test e2e-azure
/test e2e-azure-csi
/test e2e-azure-file-csi
/test e2e-azure-file-nfs-csi
/test e2e-azure-ovn-upgrade
/test e2e-gcp
/test e2e-gcp-csi
/test e2e-gcp-ovn-upgrade

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-csi-extended
/test e2e-azure-csi-extended
/test e2e-azure-csi-hypershift
/test e2e-azure-file-csi-extended
/test e2e-azure-file-csi-hypershift
/test e2e-azure-file-nfs-csi-hypershift
/test e2e-azurestack-csi

@dobsonj

dobsonj commented Jul 24, 2026

Copy link
Copy Markdown
Member

/retest

@mpatlasov

Copy link
Copy Markdown
Contributor Author

/verified by mpatlasov

  1. Installed cluster by ClusterBot: launch 5.0,openshift/csi-operator#584 gcp

  2. Check that csi drv pods are up and running:

gcp-pd-csi-driver-controller-7fc5cff998-dbnbn                     10/10   Running     0             32m
gcp-pd-csi-driver-controller-7fc5cff998-r5nld                     10/10   Running     0             33m
gcp-pd-csi-driver-node-297fd                                      3/3     Running     0             25m
gcp-pd-csi-driver-node-dm2jr                                      3/3     Running     0             33m
gcp-pd-csi-driver-node-drgwb                                      3/3     Running     3 (23m ago)   25m
gcp-pd-csi-driver-node-gfj99                                      3/3     Running     0             33m
gcp-pd-csi-driver-node-l8rkz                                      3/3     Running     0             25m
gcp-pd-csi-driver-node-wjbd6                                      3/3     Running     0             33m
gcp-pd-csi-driver-operator-755f7948d6-x7xfk                       1/1     Running     0             33m
  1. Apply simple static pod yaml to see that volume can be allocated:
$ oc apply -f fedora-w-claim1-default-sc-1024Gi.yaml

$ oc exec -it fedora -- df /mnt/claim1
Filesystem      1K-blocks  Used  Available Use% Mounted on
/dev/sdb       1055762868    28 1055746456   1% /mnt/claim1
  1. Verified the sequence of actions performed by gcp-pd operator: firstly apply prerequisites, then start controllers:
$ oc logs -n openshift-cluster-csi-drivers gcp-pd-csi-driver-operator-755f7948d6-x7xfk |grep -E "Created Deployment.apps/gcp-pd-csi-driver-controller|gcp-pd-csi-driver-controller-sa|gcp-pd-hostnetwork-role|gcp-pd-controller-hostnetwork-binding|Starting.*GCPPDDriverControlPlaneStaticResourcesController-StaticResources|Starting.*GCPPDDriverControllerServiceController|prerequisite"
...
I0724 22:25:52.760647       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/controller_sa.yaml (changed=true)
I0724 22:25:52.760673       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/node_sa.yaml (changed=true)
I0724 22:25:52.760678       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/hostnetwork_role.yaml (changed=true)
I0724 22:25:52.760681       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/controller_hostnetwork_binding.yaml (changed=true)
I0724 22:25:52.760686       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/privileged_role.yaml (changed=true)
I0724 22:25:52.760690       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/node_privileged_binding.yaml (changed=true)
I0724 22:25:52.760697       1 prerequisites.go:31] All prerequisite assets are applied
I0724 22:25:52.762942       1 base_controller.go:119] Starting #1 worker of GCPPDDriverControlPlaneStaticResourcesController-StaticResources controller ...
I0724 22:25:52.763084       1 base_controller.go:119] Starting #1 worker of GCPPDDriverControllerServiceController controller ...
I0724 22:25:52.841827       1 event.go:377] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-cluster-csi-drivers", Name:"gcp-pd-csi-driver-operator", UID:"b8501317-3169-41a1-b610-3f5de34c79e2", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'DeploymentCreated' Created Deployment.apps/gcp-pd-csi-driver-controller -n openshift-cluster-csi-drivers because it was missing
  1. Verified that the list of events in csi driver namespace does not contain problematic messages (see OCPBUG for full message):
$ oc get event -n openshift-cluster-csi-drivers -o yaml |grep "unable to validate against" |wc -l
0

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

Copy link
Copy Markdown

@mpatlasov: This PR has been marked as verified by mpatlasov.

Details

In response to this:

/verified by mpatlasov

  1. Installed cluster by ClusterBot: launch 5.0,openshift/csi-operator#584 gcp

  2. Check that csi drv pods are up and running:

gcp-pd-csi-driver-controller-7fc5cff998-dbnbn                     10/10   Running     0             32m
gcp-pd-csi-driver-controller-7fc5cff998-r5nld                     10/10   Running     0             33m
gcp-pd-csi-driver-node-297fd                                      3/3     Running     0             25m
gcp-pd-csi-driver-node-dm2jr                                      3/3     Running     0             33m
gcp-pd-csi-driver-node-drgwb                                      3/3     Running     3 (23m ago)   25m
gcp-pd-csi-driver-node-gfj99                                      3/3     Running     0             33m
gcp-pd-csi-driver-node-l8rkz                                      3/3     Running     0             25m
gcp-pd-csi-driver-node-wjbd6                                      3/3     Running     0             33m
gcp-pd-csi-driver-operator-755f7948d6-x7xfk                       1/1     Running     0             33m
  1. Apply simple static pod yaml to see that volume can be allocated:
$ oc apply -f fedora-w-claim1-default-sc-1024Gi.yaml

$ oc exec -it fedora -- df /mnt/claim1
Filesystem      1K-blocks  Used  Available Use% Mounted on
/dev/sdb       1055762868    28 1055746456   1% /mnt/claim1
  1. Verified the sequence of actions performed by gcp-pd operator: firstly apply prerequisites, then start controllers:
$ oc logs -n openshift-cluster-csi-drivers gcp-pd-csi-driver-operator-755f7948d6-x7xfk |grep -E "Created Deployment.apps/gcp-pd-csi-driver-controller|gcp-pd-csi-driver-controller-sa|gcp-pd-hostnetwork-role|gcp-pd-controller-hostnetwork-binding|Starting.*GCPPDDriverControlPlaneStaticResourcesController-StaticResources|Starting.*GCPPDDriverControllerServiceController|prerequisite"
...
I0724 22:25:52.760647       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/controller_sa.yaml (changed=true)
I0724 22:25:52.760673       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/node_sa.yaml (changed=true)
I0724 22:25:52.760678       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/hostnetwork_role.yaml (changed=true)
I0724 22:25:52.760681       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/controller_hostnetwork_binding.yaml (changed=true)
I0724 22:25:52.760686       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/privileged_role.yaml (changed=true)
I0724 22:25:52.760690       1 prerequisites.go:49] Applied prerequisite asset overlays/gcp-pd/generated/standalone/node_privileged_binding.yaml (changed=true)
I0724 22:25:52.760697       1 prerequisites.go:31] All prerequisite assets are applied
I0724 22:25:52.762942       1 base_controller.go:119] Starting #1 worker of GCPPDDriverControlPlaneStaticResourcesController-StaticResources controller ...
I0724 22:25:52.763084       1 base_controller.go:119] Starting #1 worker of GCPPDDriverControllerServiceController controller ...
I0724 22:25:52.841827       1 event.go:377] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-cluster-csi-drivers", Name:"gcp-pd-csi-driver-operator", UID:"b8501317-3169-41a1-b610-3f5de34c79e2", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'DeploymentCreated' Created Deployment.apps/gcp-pd-csi-driver-controller -n openshift-cluster-csi-drivers because it was missing
  1. Verified that the list of events in csi driver namespace does not contain problematic messages (see OCPBUG for full message):
$ oc get event -n openshift-cluster-csi-drivers -o yaml |grep "unable to validate against" |wc -l
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.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 1da4798 and 2 for PR HEAD d6b5c3b in total

@mpatlasov

Copy link
Copy Markdown
Contributor Author

/retest-required

@mpatlasov

Copy link
Copy Markdown
Contributor Author

/retest-required

@mpatlasov

Copy link
Copy Markdown
Contributor Author

/test e2e-azure

@mpatlasov

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-upgrade

@mpatlasov

Copy link
Copy Markdown
Contributor Author

/test e2e-azure

@mpatlasov

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-ovn-upgrade

@openshift-ci

openshift-ci Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

@mpatlasov: The following tests 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/aws-efs-single-zone-operator-e2e-extended d6b5c3b link false /test aws-efs-single-zone-operator-e2e-extended
ci/prow/e2e-azure-file-csi-hypershift d6b5c3b link false /test e2e-azure-file-csi-hypershift
ci/prow/smb-win2019-operator-e2e d6b5c3b link false /test smb-win2019-operator-e2e
ci/prow/e2e-azure-csi-hypershift d6b5c3b link false /test e2e-azure-csi-hypershift
ci/prow/aws-efs-sts-cross-account-operator-e2e d6b5c3b link false /test aws-efs-sts-cross-account-operator-e2e
ci/prow/aws-efs-operator-e2e-extended d6b5c3b link false /test aws-efs-operator-e2e-extended
ci/prow/smb-win2022-operator-e2e d6b5c3b link false /test smb-win2022-operator-e2e
ci/prow/e2e-aws-ovn-upgrade d6b5c3b link true /test e2e-aws-ovn-upgrade
ci/prow/e2e-azure-csi-extended d6b5c3b link false /test e2e-azure-csi-extended
ci/prow/e2e-aws-csi-extended d6b5c3b link false /test e2e-aws-csi-extended
ci/prow/e2e-azure-file-csi-extended d6b5c3b link false /test e2e-azure-file-csi-extended
ci/prow/e2e-azurestack-csi d6b5c3b link false /test e2e-azurestack-csi
ci/prow/e2e-azure d6b5c3b link true /test e2e-azure
ci/prow/e2e-gcp-ovn-upgrade d6b5c3b link true /test e2e-gcp-ovn-upgrade
ci/prow/e2e-azure-file-nfs-csi-hypershift d6b5c3b link false /test e2e-azure-file-nfs-csi-hypershift

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants