Playground shows nodes are down when public key missing from twin

[elproducto]

Description

Unable to deploy a micro VM on test playground. Error Node is down is presented once node is selected, however node is marked as online in the test dashboard. Brave and Chrome browser was used to deploy on grid.

Issue only appears on test playground. I was able to deploy a Micro VM to production playground with same browsers and seed phrase. Production playground is using v1.6.1 of playground, test is using v1.7.0-rc3 of playground.

Steps to reproduce

• Navigate to test dashboard Node Section - Note an online Node ID
• Navigate to test playground
• In Brave browser toggled Shield down, not required for Chrome
• Select Micro Virtual machine link
• Click Profile Manager link
• Input seed phrase into Profile Manager
• Inpute VM specification
• Select node or Input Node ID from above to deploy VM to (Tested against several nodes, but one can use FreeFarm Nodes,Node 12, or Node 262 to reproduce)

[scottyeager]

So I thought that this was happening because the dashboard didn't set the public key ([#630 ])(threefoldtecharchive/tfgrid_dashboard#630).

Since originally writing this comment, I've learned that:

1. The playground should set the public key and relay automatically
2. The case where the public key does not get set is not universally reproducible and it's not been observed on mainnet since the playground 1.7.0 was released there

[scottyeager]

The outstanding question is, why do some accounts on testnet not have their twin and relay set automatically. For example, I've activated this account in the profile:

But the relay doesn't get set:

And this happens on new accounts I create on testnet too.

[AhmedHanafy725]

same as

• capacity filter not working with incorrect format pk  #88

[A-Harby]

PK issue was fixed and if pk is empty or incorrect, it will update once weblets is used.
And If relay isn't defined yet, user wouldn't be able to open until twin relay is set.