Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCPBUGS-54180: Disable remove-not-ready-taint for azure disk csi driver #371

Merged
merged 1 commit into from
Mar 30, 2025

Conversation

Phaow
Copy link
Contributor

@Phaow Phaow commented Mar 25, 2025

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 25, 2025
@openshift-ci openshift-ci bot requested review from mpatlasov and tsmetana March 25, 2025 09:57
@Phaow Phaow changed the title [WIP] Fix: disable remove-not-ready-taint for azure disk csi driver OCPBUGS-54180: [WIP] Fix: disable remove-not-ready-taint for azure disk csi driver Mar 27, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 27, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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 Mar 27, 2025
@openshift-ci-robot
Copy link

@Phaow: This pull request references Jira Issue OCPBUGS-54180, which is invalid:

  • expected the bug to target the "4.19.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.

In response to this:

  • don't merge.

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
Contributor Author

Phaow commented Mar 27, 2025

/retest

@Phaow Phaow changed the title OCPBUGS-54180: [WIP] Fix: disable remove-not-ready-taint for azure disk csi driver OCPBUGS-54180: Disable remove-not-ready-taint for azure disk csi driver Mar 27, 2025
@Phaow
Copy link
Contributor Author

Phaow commented Mar 27, 2025

/jira refresh

@openshift-ci-robot 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 Mar 27, 2025
@openshift-ci-robot
Copy link

@Phaow: This pull request references Jira Issue OCPBUGS-54180, 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.19.0) matches configured target version for branch (4.19.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.

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

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.

@Phaow
Copy link
Contributor Author

Phaow commented Mar 27, 2025

Hi @gnufied @mpatlasov , could you help take a look when you get a chance? Thank you!

@Phaow
Copy link
Contributor Author

Phaow commented Mar 27, 2025

/assign @gnufied @mpatlasov

@openshift-ci-robot
Copy link

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, 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.

In 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.

@@ -23,6 +23,9 @@ spec:
# Use credentials provided by the azure-inject-credentials container
- --cloud-config-secret-name=""
- --cloud-config-secret-namespace=""
# Disable the remove-not-ready-taint, as it is not implemented in ocp
# https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2309
- --remove-not-ready-taint=false
Copy link
Member

Choose a reason for hiding this comment

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

Does controller part need anything?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

From my test result, from controller part, nothing else needed. In addition from upstream review https://github.com/kubernetes-sigs/azuredisk-csi-driver/pull/2976/files add the arg to the driver node is enough.

Copy link
Member

Choose a reason for hiding this comment

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

/lgtm
/approve

@Phaow Phaow requested a review from gnufied March 28, 2025 01:26
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 28, 2025
Copy link
Contributor

openshift-ci bot commented Mar 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gnufied, Phaow

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 Mar 28, 2025
@Phaow
Copy link
Contributor Author

Phaow commented Mar 28, 2025

From CI logs I could see the unexpected permission issue and drain node action disable.
/label acknowledge-critical-fixes-only
/label qe-approved

@openshift-ci openshift-ci bot added acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. qe-approved Signifies that QE has signed off on this PR labels Mar 28, 2025
@openshift-ci-robot
Copy link

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Phaow

In 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.

Copy link
Contributor

openshift-ci bot commented Mar 28, 2025

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: Phaow.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Phaow

In 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.

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-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 40900e2 and 2 for PR HEAD a88157b in total

@Phaow
Copy link
Contributor Author

Phaow commented Mar 28, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 40900e2 and 2 for PR HEAD a88157b in total

@Phaow
Copy link
Contributor Author

Phaow commented Mar 28, 2025

/retest-required

1 similar comment
@Phaow
Copy link
Contributor Author

Phaow commented Mar 28, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 40900e2 and 2 for PR HEAD a88157b in total

Copy link
Contributor

openshift-ci bot commented Mar 28, 2025

@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-azure-csi-extended a88157b link false /test e2e-azure-csi-extended
ci/prow/okd-scos-e2e-aws-ovn a88157b link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-azurestack-csi a88157b link false /test e2e-azurestack-csi

Full PR test history. Your PR dashboard.

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.

@Phaow
Copy link
Contributor Author

Phaow commented Mar 30, 2025

/retest-required

@openshift-merge-bot openshift-merge-bot bot merged commit 54b9f05 into openshift:main Mar 30, 2025
20 of 23 checks passed
@openshift-ci-robot
Copy link

@Phaow: Jira Issue OCPBUGS-54180: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-54180 has been moved to the MODIFIED state.

In 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate 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. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants