-
Notifications
You must be signed in to change notification settings - Fork 8
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]: A lot of nodes with fake GPU cards on mainnet #2770
Comments
Investigation and Solution:it took me sometime to set up mainnet locally as there're some relay updates that's not available on mainnet Issue is reproducible on same node, still investigating what's causing this |
It could be a builtin GPU not an external one @muhamadazmy correct? |
I don't believe this is a built in GPU. You can always google the model using the GPU identity string suffix. So by looking up https://www.techpowerup.com/vgabios/236303/gigabyte-rtx3070-8192-210526 Failure to deploy can be duo other reasons. It would be very useful if we can collect the deployment status after failure (get the changes, to the deployment from the node) not only the final status. This will give more details on what exactly happened. Would be also very useful if we could collect node logs at the same time of the problem. Since i have no idea when this deployment was created it's not possible to find the corresponding node logs. In general the node logs looks normal, and I don't believe it's fake. |
After some investigation, I noticed that the deployment with gpu crashes, I opened an issue for this I also noticed that the vm isn't listed but the contract doesn't get deleted |
the issue happened on the node so nothing can be done here |
Is there an existing issue for this?
which package/s did you face the problem with?
Dashboard
What happened?
I tried deploying a VM on a node with a GPU after renting it, but it kept failing to deploy a lot, and even when it did, I couldn't ssh to the VM.
A lot of the nodes with GPUs, either one or more, are fake or have a problem deploying or connecting to them.
Steps To Reproduce
No response
which network/s did you face the problem on?
Main
version
2.4.2
Twin ID/s
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant screenshots/screen records
Relevant log output
The text was updated successfully, but these errors were encountered: