🐞 [Bug]: Deployment is stuck at validating Nodes on the Dashboard, and the old deployment lists are not visible.

[mahendravarmayadala93]

Is there an existing issue for this?

• [X] I have searched the existing issues

which package/s did you face the problem with?

Dashboard

What happened?

Mat is unable to connect to a VM on Node ID 687 due to the deployed list is not visible on his dashboard which he deployed 6 months back. Also, check the specific issue for this showing logs.. This issue follows a previous issue where deployments were also not displayed.

He attempted to deploy a new VM on Node ID 687, but the process is stuck on node validation.

A testing video is available for reference from our side where In contrast Scott , Sherwin, Shang, and I successfully deployed on Node ID 687 without any issues, and the process went smoothly.

Also, here are the errors on the client side on his browser console while trying to deploy on his Node : 687

We tested the same between Node 687 & Node 1, you can see the difference in errors

Steps To Reproduce

1) Open Dashboard

2) After you login click on Side menu, and click on Deploy and then choose Virtual machines

3) Choose any one of the VM

4) Select Nodes manually and then choose the Node 687

5) Then click on deploy.

which network/s did you face the problem on?

Main

version

NA

Twin ID/s

NA

Node ID/s

687

Farm ID/s

209

Contract ID/s

NA

Relevant screenshots/screen records

Here's the screen record on Client side while deploying VM on the Node 687 : https://drive.google.com/file/d/1rcWeU59E6SXyKpFc88SdB9Fmnd1om31u/view?usp=sharing

Relevant log output

NA

[TullysInc]

Update from the farmer: https://t.me/threefoldtesting/15012

He is now unable to deploy a VM on any node in Poland.

[Cameron1986labeyrie]

Update from Farmer on Crisp:

• The user is still unable to deploy on his own node_687.
• Strangely the issue is occuring with any node he chooses in Poland.

[scottyeager]

The user reports that they are able to create deployments after creating a new account.

I suspect that the issue may be with the RMB public key set on tfchain for the original account.

[AhmedHanafy725]

I suspect that the issue may be with the RMB public key set on tfchain for the original account.

sound yes. but the dashboard auto-updates the public key once login if it's incorrect. so what is the twin ID of the old account?

[scottyeager]

Right, I would have expected the public key to get updated too, especially since the user logged in again using incognito tabs and also tried multiple browsers.

The twin id is 737.

[AhmedHanafy725]

could be this cache issue as explained here https://github.com/threefoldtech/rmb-rs/issues/200#issuecomment-2435549736