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

[BUG]: CSM PowerMax wrong error message #1634

Open
anurajpd opened this issue Dec 9, 2024 · 1 comment
Open

[BUG]: CSM PowerMax wrong error message #1634

anurajpd opened this issue Dec 9, 2024 · 1 comment
Labels
needs-triage Issue requires triage. type/bug Something isn't working. This is the default label associated with a bug issue.

Comments

@anurajpd
Copy link

anurajpd commented Dec 9, 2024

Bug Description

Wrong error message when the worker node is already registered in the PowerMax.

Logs

time="2024-12-09T09:44:11Z" level=info msg="/csi.v1.Node/NodeGetInfo: REQ 0008: XXX_NoUnkeyedLiteral={}, XXX_sizecache=0"
time="2024-12-09T09:44:11Z" level=error msg="GetPortGroupByID failed: Port group None not found on 000497900413"
time="2024-12-09T09:44:11Z" level=error msg="unable to fetch ip interfaces for 000497900413: Port group None not found on 000497900413"
time="2024-12-09T09:44:11Z" level=error msg="No topology keys could be generated"
time="2024-12-09T09:44:11Z" level=info msg="/csi.v1.Node/NodeGetInfo: REP 0008: rpc error: code = FailedPrecondition desc = no topology keys could be generate"

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

Register the worker node with the PowerMax before deploying the CSM

Expected Behavior

If the nodes are already registered the CSM should be able to use those and continue or at least faile with proper error message

CSM Driver(s)

CSM 1.12 PowerMax

Installation Type

CSM Operator

Container Storage Modules Enabled

No response

Container Orchestrator

OpenShift 4.17

Operating System

CoreOS

@anurajpd anurajpd added needs-triage Issue requires triage. type/bug Something isn't working. This is the default label associated with a bug issue. labels Dec 9, 2024
@csmbot
Copy link
Collaborator

csmbot commented Dec 9, 2024

@anurajpd: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately.


We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Issue requires triage. type/bug Something isn't working. This is the default label associated with a bug issue.
Projects
None yet
Development

No branches or pull requests

2 participants