search

threefoldtech / home

Starting point for the threefoldtech organization
https://threefold.io
Apache License 2.0
9 stars 4 forks source link

GE: SDK Solution Expose: Something wrong happened, please contact support #810

Closed joefoxton closed 4 years ago

joefoxton commented 4 years ago

We were running a trial deploy of Artheon's workload this morning, and hit this Solution Expose snag. To reproduce, I selection "Solution Expose" from the menu, then "Create New", then I get the error in the screen shot below. Please note this other symptom - not sure if its related: https://github.com/threefoldtech/home/issues/808

Here's the screenshot, and browser log:

Screenshot 2020-06-24 at 15 52 34

localhost-1593007070842.log

weynandkuijpers commented 4 years ago

:4000/zerobot/admin/actors/wallet/get_wallets:1 Failed to load resource: the server responded with a status of 400 (Bad Request)

Not being a developer but reading through the log report I think the absence of the wallets in the GUI are the cause. The wallets should still be part of the container, you can check this by doing in the 3sdk executable:

threebot shell

which get you in the shell. Open a kosmos shell:

kosmos

and then check the wallets available:

Screen Shot 2020-06-24 at 4 34 46 PM

they should still be available in the container.

To get them back in the GUI maybe you can import the secret again, however, I am not sure about that as this is not something that I have ever tried.

joefoxton commented 4 years ago

Yep they are still available… this is how we were able to get through the provisioning steps

On 24 Jun 2020, at 16:35, Weynand Kuijpers notifications@github.com wrote:

:4000/zerobot/admin/actors/wallet/get_wallets:1 Failed to load resource: the server responded with a status of 400 (Bad Request)

Not being a developer but reading through the log report I think the absence of the wallets in the GUI are the cause. The wallets should still be part of the container, you can check this by doing in the 3sdk executable:

threebot shell which get you in the shell. Open a kosmos shell:

kosmos and then check the wallets available:

they should still be available in the container.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/threefoldtech/home/issues/810#issuecomment-648859898, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJREDS5DYKQ57WS6RXEJP3RYIFMRANCNFSM4OGWD7WQ.

joefoxton commented 4 years ago

This was caused by the errant entry of an invalid wallet secret. That problem has been fixed elsewhere, so closing this.