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

rdma-core did not take effect after installation, spiderpool-agent did not generate the corresponding rdma indicator #4265

Closed
ty-dc opened this issue Nov 4, 2024 · 2 comments
Closed

rdma-core did not take effect after installation, spiderpool-agent did not generate the corresponding rdma indicator #4265

ty-dc opened this issue Nov 4, 2024 · 2 comments
Assignees
@lou-lan @ty-dc
Labels
kind/bug priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@ty-dc
Copy link
Collaborator

ty-dc commented Nov 4, 2024

Spiderpool Version

latest

Main CNI

any

bug description

{"level":"ERROR","ts":"2024-11-04T10:14:25.846Z","logger":"rdma-metrics-exporter","caller":"rdmametrics/metrics.go:295","msg":"failed to get RDMA stats","net_ns_id":"cni-c82a677c-ab67-5ac4-a990-78429556998c","error":"error executing 'rdma statistic -j' command: executable file not found in $PATH"}

What did you expect to happen?

No response

How to reproduce it (as minimally and precisely as possible)

No response

Additional Context

No response
@ty-dc ty-dc added the kind/bug label Nov 4, 2024
@ty-dc ty-dc changed the title The installation of rdma-core failed, spiderpool-agent did not generate the corresponding rdma indicator, rdma-core did not take effect after installation, spiderpool-agent did not generate the corresponding rdma indicator Nov 4, 2024
@lou-lan
Copy link
Collaborator

lou-lan commented Nov 5, 2024

ref #4263

@ty-dc
Copy link
Collaborator Author

ty-dc commented Nov 27, 2024 •
edited
Loading

#4263

@ty-dc ty-dc closed this as completed Nov 27, 2024
@ty-dc ty-dc added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lou-lan lou-lan

@ty-dc ty-dc

Labels
kind/bug priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lou-lan @ty-dc