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

controller: Do not check volume status if we do not have permission #49

Merged

Conversation

Vicente-Cheng
Copy link
Collaborator

IMPORTANT: Please do not create a Pull Request without creating an issue first.

Problem:
The new csi driver did not work if the corresponding clusterrole did not have the correct permission.

Solution:
Skip the volume status checking if the clusterrole did not have corresponding permission.

Related Issue:
harvester/harvester#6849

Test plan:

  1. create v1.3.2 cluster
  2. use the CSI driver with this PR. The PVC operation should work as usual.

@bk201 bk201 changed the title controller: Donot check volume status if we donot have permission controller: Do not check volume status if we donot have permission Nov 8, 2024
@Vicente-Cheng Vicente-Cheng marked this pull request as draft November 8, 2024 08:29
@Vicente-Cheng Vicente-Cheng marked this pull request as ready for review November 10, 2024 12:49
    - Also, remove the redundant lhclient on node server

Signed-off-by: Vicente Cheng <[email protected]>
@bk201 bk201 changed the title controller: Do not check volume status if we donot have permission controller: Do not check volume status if we do not have permission Nov 12, 2024
Copy link
Member

@WebberHuang1118 WebberHuang1118 left a comment

Choose a reason for hiding this comment

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

LGTM, thanks.

@WebberHuang1118 WebberHuang1118 merged commit 19d7743 into harvester:master Nov 12, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants