-
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
🐞 [QANET] [Bug]: Failed to deploy on a Standby nodes #3730
Comments
Related to: #3332 |
messages should indicate that: 1- if the node is standby and the user want to deploy on it; a message should say you cant use this node to deploy you should first reserve it. 2- if the nodes is reserved and still in stand by; a message should tell user to wait until the node come up. 3- if press the reserve button show a message that declares this node will take sometime to go UP. |
|
used nodestatus enum from gridproxy instead of string comparison |
standby1.mp4standby2.mp4Related Link: |
Is there an existing issue for this?
which package/s did you face the problem with?
Dashboard
What happened?
#when select a standby node manually on dashboard to deploy on it; I got two different behaviors:
1- On Testnet:
2- On Mainnet:
Steps To Reproduce
open dashboard
go to node finder
filter with standby fitler and get a standby node ID
go to deploy micro VM page
select node manually
use the standby node ID
then it will fail with this error:
which network/s did you face the problem on?
Test, Main
version
2.6.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: