Skip to content
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

Closed
1 task done
ramezsaeed opened this issue Dec 9, 2024 · 5 comments
Closed
1 task done

🐞 [QANET] [Bug]: Failed to deploy on a Standby nodes #3730

ramezsaeed opened this issue Dec 9, 2024 · 5 comments
Assignees
Labels
type_bug Something isn't working
Milestone

Comments

@ramezsaeed
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

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:

  • the node validation passed
  • the deployment failed
  • the node status changed to Up within 5 min.
    Screenshot from 2024-12-09 16-11-05
    Screenshot from 2024-12-09 16-10-06

2- On Mainnet:

  • the node validation doesn't passes and failed with this error:
  • the node didn't go to UP status even after 1 hour
  • I can do reserve the node while its in standby state but fail to deploy on it.
    Screenshot from 2024-12-09 16-04-16
    Screenshot from 2024-12-09 16-03-25
    Screenshot from 2024-12-09 15-28-36

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:

Error getting node 6656 Failed to send request to twinId 12162 with command: zos.storage.pools, payload: Didn't get a response after 20 seconds

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

--
@ramezsaeed ramezsaeed added the type_bug Something isn't working label Dec 9, 2024
@ramezsaeed
Copy link
Contributor Author

Related to: #3332

@ramezsaeed
Copy link
Contributor Author

ramezsaeed commented Dec 11, 2024

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.

@ramezsaeed ramezsaeed added this to the 2.7.0 milestone Dec 11, 2024
@amiraabouhadid amiraabouhadid self-assigned this Dec 22, 2024
@amiraabouhadid
Copy link
Contributor

  • updated err msgs based on status and reserve
  • added toast on reserve of standby
  • will run more tests

@amiraabouhadid
Copy link
Contributor

used nodestatus enum from gridproxy instead of string comparison

@khaledyoussef24 khaledyoussef24 changed the title 🐞 [Bug]: Failed to deploy on a Standby nodes 🐞 [QANET] [Bug]: Failed to deploy on a Standby nodes Dec 30, 2024
@atefnazmy
Copy link

  • Verified on Dev,
  • Version: c6fad22
  • The Toast for standby reserving is added and the Error messages for status & standby have been updated.
standby1.mp4
standby2.mp4

Related Link:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type_bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants