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.

Sign up for GitHub

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

Jump to bottom

MAS MVI install ansible playbook does not check existing "NVDIA GPU Operator" #1454

Open
kalyan-nookala opened this issue Sep 6, 2024 · 1 comment
Open

MAS MVI install ansible playbook does not check existing "NVDIA GPU Operator" #1454

kalyan-nookala opened this issue Sep 6, 2024 · 1 comment
Assignees
@dclain
Labels
Bug Report Something isn't working Critical - Tracked in Jira Issues that have been escalated internally and are tracked in Jira now
Milestone
November 2024

Comments

@kalyan-nookala
Copy link

Collection version

ibm.mas_devops 22.5.2

Environment information

quay.io/ibmmas/cli:10.9.2

What happened?

NVIDI GPU Operator: Same as above, the ansible script overwrites “cluster policy” on a healthy and working operator with another version of GPU driver and makes it to go to “not ready” status.

Relevant log output

n/a
@kalyan-nookala kalyan-nookala added the Bug Report Something isn't working label Sep 6, 2024
@durera durera added the Critical - Tracked in Jira Issues that have been escalated internally and are tracked in Jira now label Nov 1, 2024
@durera
Copy link
Contributor

durera commented Nov 1, 2024

https://jsw.ibm.com/browse/MASCORE-4342

@durera durera added this to the November 2024 milestone Nov 1, 2024
@dclain dclain self-assigned this Nov 15, 2024
dclain added a commit that referenced this issue Nov 15, 2024
@dclain
[patch] Skip GPU setup if cluster policy is ready
d2f0bc4 
#1454
@dclain dclain mentioned this issue Nov 15, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dclain dclain

Labels
Bug Report Something isn't working Critical - Tracked in Jira Issues that have been escalated internally and are tracked in Jira now
Projects
None yet
Milestone
November 2024
Development

No branches or pull requests
3 participants
@dclain @durera @kalyan-nookala