Skip to content

OCPBUGS-78576: UPSTREAM: 136913: Update the csi-driver-host-path version to 1.17.1#2629

Closed
Phaow wants to merge 1 commit intoopenshift:masterfrom
Phaow:ci-fix
Closed

OCPBUGS-78576: UPSTREAM: 136913: Update the csi-driver-host-path version to 1.17.1#2629
Phaow wants to merge 1 commit intoopenshift:masterfrom
Phaow:ci-fix

Conversation

@Phaow
Copy link
Copy Markdown

@Phaow Phaow commented Mar 17, 2026

What type of PR is this?

/kind bug

What this PR does / why we need it:

Which issue(s) this PR is related to:

Fixes https://redhat.atlassian.net/browse/OCPBUGS-78576.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@openshift-ci-robot openshift-ci-robot added the backports/validated-commits Indicates that all commits come to merged upstream PRs. label Mar 17, 2026
@openshift-ci openshift-ci Bot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 17, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 17, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: This pull request references Jira Issue OCPBUGS-78576, 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)

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

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Which issue(s) this PR is related to:

Fixes https://redhat.atlassian.net/browse/OCPBUGS-78576.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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
Copy link
Copy Markdown

@Phaow: the contents of this pull request could be automatically validated.

The following commits are valid:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci Bot requested review from jerpeter1 and tkashem March 17, 2026 05:56
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 17, 2026

Walkthrough

Multiple CSI hostpath plugin image tags were updated to v1.17.1 in test manifests; the DRA test driver pod image was made unpinned and deployment code was changed to compute and patch the hostpathplugin image dynamically during setup.

Changes

Cohort / File(s) Summary
CSI test manifests
test/e2e/testing-manifests/storage-csi/external-snapshotter/volume-group-snapshots/csi-hostpath-plugin.yaml, test/e2e/testing-manifests/storage-csi/hostpath/hostpath/csi-hostpath-plugin.yaml, test/e2e/testing-manifests/storage-csi/mock/csi-mock-driver.yaml, test/e2e/testing-manifests/storage-csi/mock/csi-mock-proxy.yaml
Updated registry.k8s.io/sig-storage/hostpathplugin container image tags to v1.17.1 (previous tags were v1.16.1 or v1.17.0). No other container fields changed.
DRA deploy code
test/e2e/dra/utils/deploy.go
Added logic to select the latest registry.k8s.io/sig-storage/hostpathplugin:<version> from image configs, replace registry in the image URL, and patch the ReplicaSet/Replica template container image at manifest mutation time. Moved manifest slice creation after image computation and adjusted error assignment.
DRA manifest (unpinned image)
test/e2e/testing-manifests/dra/dra-test-driver-proxy.yaml
Replaced pinned image registry.k8s.io/sig-storage/hostpathplugin:v1.16.1 with an unpinned registry.k8s.io/sig-storage/hostpathplugin (comment notes runtime patching). No other fields changed.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 17, 2026

/hold
The PR is ready for review but we still needs mirroring the new upstream test image registry.k8s.io/sig-storage/hostpathplugin:v1.17.1(quay.io/openshift/community-e2e-images:e2e-33-registry-k8s-io-sig-storage-hostpathplugin-v1-17-1-thKi_291aDqGI3Q7) before merging. The e2e-aws-ovn-techpreview-serial jobs will be always failed before we finished the mirroring.

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 17, 2026
@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 17, 2026

Hi @jsafrane , could you help take a look when you get a chance? Thank you!^^

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 17, 2026

/assign @jsafrane

@jsafrane
Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 18, 2026
@jubittajohn
Copy link
Copy Markdown

/test images

@jacobsee
Copy link
Copy Markdown
Member

/retest

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 19, 2026

/retest-required

1 similar comment
@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 19, 2026

/retest-required

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 19, 2026

/retest

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 20, 2026

/verified by CI
I could see after mirror succeed vgs tests(VolumeGroupSnapshottable should create snapshots for StatefulSet volumes and verify data consistency after restore) passed in e2e-aws-ovn-techpreview job.

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 20, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI
I could see after mirror succeed vgs tests(VolumeGroupSnapshottable should create snapshots for StatefulSet volumes and verify data consistency after restore) passed in e2e-aws-ovn-techpreview job.

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.

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 20, 2026

/retest-required

1 similar comment
@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 20, 2026

/retest-required

@jsafrane
Copy link
Copy Markdown

e2e-aws-ovn-serial-2of2 fails with:

reading manifest e2e-48-registry-k8s-io-e2e-test-images-busybox-1-36-1-1-n3BezCOfxp98l84K in quay.io/openshift/community-e2e-images: manifest unknown

But this PR does not add / change busybox image
/retest

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 20, 2026

Threre are many flaky tests ... , when I check the job history and found fixes are in progress ->

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 21, 2026

/retest

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 23, 2026

/retest

1 similar comment
@Phaow
Copy link
Copy Markdown
Author

Phaow commented Mar 23, 2026

/retest

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 26, 2026
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Mar 26, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 26, 2026

New changes are detected. LGTM label has been removed.

@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: the contents of this pull request could be automatically validated.

The following commits are valid:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 26, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jsafrane, Phaow
Once this PR has been reviewed and has the lgtm label, please assign tkashem for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Apr 1, 2026

/retest

@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: the contents of this pull request could be automatically validated.

The following commits are valid:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: the contents of this pull request could be automatically validated.

The following commits are valid:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@test/e2e/dra/utils/deploy.go`:
- Around line 482-487: The code uses lexicographic string comparison to pick the
newest hostPath tag; replace that with proper semantic version comparison using
golang.org/x/mod/semver: import "golang.org/x/mod/semver" and change the
condition to treat empty hostPathVersion as older or when
semver.Compare(hostPathVersion, version) < 0 (ensure inputs are valid semver,
e.g. semver.IsValid(hostPathVersion) and semver.IsValid(version) or normalize
with a "v" prefix) so hostPathVersion = version only when hostPathVersion is
empty or semver.Compare(hostPathVersion, version) < 0; keep references to the
hostPathVersion and version variables unchanged.
🪄 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 141ac495-d582-400e-ac1c-dc38cf994d7a

📥 Commits

Reviewing files that changed from the base of the PR and between 7debbef and 78ed1fc.

📒 Files selected for processing (2)
  • test/e2e/dra/utils/deploy.go
  • test/e2e/testing-manifests/dra/dra-test-driver-proxy.yaml

Comment thread test/e2e/dra/utils/deploy.go Outdated
Comment on lines +482 to +487
// "Dumb" string comparison is good enough for e.g. v1.16.1 < v1.17.0.
// It seems unlikely that any major/patch will need more than one digit
// or that version grow beyond 99.
if hostPathVersion == "" || hostPathVersion < version {
hostPathVersion = version
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Don't use lexicographic ordering for the "latest" hostpath tag.

hostPathVersion < version will misorder semantic versions once a component reaches two digits (v1.17.9 sorts above v1.17.10). That means this helper can silently select an older hostpath image even though its job here is to follow the newest storage-csi version.

Suggested fix
-		// "Dumb" string comparison is good enough for e.g. v1.16.1 < v1.17.0.
-		// It seems unlikely that any major/patch will need more than one digit
-		// or that version grow beyond 99.
-		if hostPathVersion == "" || hostPathVersion < version {
+		if hostPathVersion == "" || semver.Compare(version, hostPathVersion) > 0 {
 			hostPathVersion = version
 		}
import "golang.org/x/mod/semver"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@test/e2e/dra/utils/deploy.go` around lines 482 - 487, The code uses
lexicographic string comparison to pick the newest hostPath tag; replace that
with proper semantic version comparison using golang.org/x/mod/semver: import
"golang.org/x/mod/semver" and change the condition to treat empty
hostPathVersion as older or when semver.Compare(hostPathVersion, version) < 0
(ensure inputs are valid semver, e.g. semver.IsValid(hostPathVersion) and
semver.IsValid(version) or normalize with a "v" prefix) so hostPathVersion =
version only when hostPathVersion is empty or semver.Compare(hostPathVersion,
version) < 0; keep references to the hostPathVersion and version variables
unchanged.

@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: This pull request references Jira Issue OCPBUGS-78576, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Which issue(s) this PR is related to:

Fixes https://redhat.atlassian.net/browse/OCPBUGS-78576.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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.

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Apr 1, 2026

/retest

@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: the contents of this pull request could be automatically validated.

The following commits are valid:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: This pull request references Jira Issue OCPBUGS-78576, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Which issue(s) this PR is related to:

Fixes https://redhat.atlassian.net/browse/OCPBUGS-78576.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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.

@Phaow
Copy link
Copy Markdown
Author

Phaow commented Apr 3, 2026

/test e2e-aws-ovn-crun

@bertinatto
Copy link
Copy Markdown
Member

/retest

@jsafrane
Copy link
Copy Markdown

jsafrane commented Apr 9, 2026

/test e2e-aws-ovn-techpreview

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 9, 2026

@Phaow: 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/e2e-aws-ovn-cgroupsv2 7debbef link true /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-crun 7debbef link true /test e2e-aws-ovn-crun
ci/prow/e2e-aws-ovn-techpreview 7debbef link false /test e2e-aws-ovn-techpreview
ci/prow/e2e-aws-ovn-serial-2of2 7debbef link true /test e2e-aws-ovn-serial-2of2
ci/prow/e2e-gcp 7debbef link true /test e2e-gcp
ci/prow/e2e-aws-ovn-techpreview-serial-1of2 7debbef link false /test e2e-aws-ovn-techpreview-serial-1of2
ci/prow/e2e-aws-ovn-fips 7debbef link true /test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-runc 7debbef link false /test e2e-aws-ovn-runc
ci/prow/e2e-aws-ovn-serial-1of2 7debbef link true /test e2e-aws-ovn-serial-1of2
ci/prow/e2e-metal-ipi-ovn-ipv6 7debbef link true /test e2e-metal-ipi-ovn-ipv6

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.

@openshift-bot
Copy link
Copy Markdown

Closing, please open a separate request if this work is still required.

@openshift-ci-robot
Copy link
Copy Markdown

@Phaow: This pull request references Jira Issue OCPBUGS-78576. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

What type of PR is this?

/kind bug

What this PR does / why we need it:

Which issue(s) this PR is related to:

Fixes https://redhat.atlassian.net/browse/OCPBUGS-78576.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


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.

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

Labels

backports/validated-commits Indicates that all commits come to merged upstream PRs. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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. kind/bug Categorizes issue or PR as related to a bug.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants