OCPBUGS-77428: Pass node name to csi-driver container#172
Conversation
openshift-ci-robot
added
jira/valid-reference
|
@noamasu: This pull request references Jira Issue OCPBUGS-77428, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
noamasu
force-pushed
the
OCPBUGS-77428/add-node-name-to-csi-driver
branch
from
cf6628a to
a8c2648
Compare
noamasu
changed the title
The upstream deploy manifest passes --node-name to the csi-driver container but the operator's node.yaml was missing it. Without it, the driver uses the short GCP instance name instead of the node name (FQDN), causing Node object lookups to fail. Signed-off-by: Noam Assouline <nassouli@redhat.com>
noamasu
force-pushed
the
OCPBUGS-77428/add-node-name-to-csi-driver
branch
from
a8c2648 to
9cd8bdb
Compare
|
/jira refresh |
openshift-ci-robot
added
the
jira/valid-bug
|
@mpatlasov: This pull request references Jira Issue OCPBUGS-77428, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (wduan@redhat.com), skipping review request. The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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
removed
the
jira/invalid-bug
|
@noamasu: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/lgtm |
openshift-ci-robot
added
the
verified
|
@mpatlasov: This PR has been marked as verified by DetailsIn response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mpatlasov, noamasu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@noamasu: Jira Issue Verification Checks: Jira Issue OCPBUGS-77428 Jira Issue OCPBUGS-77428 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
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. |
|
/cherry-pick release-4.21 |
|
@mpatlasov: new pull request created: #173 DetailsIn response to this:
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. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-03-02-153725 |
9 participants
The upstream deploy manifest passes --node-name to the csi-driver container but the operator's node.yaml was missing it. Without it, the driver uses the short GCP instance name instead of the full node name (FQDN), causing Node object lookups to fail