-
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
(QA verification) 🐞 [Bug]: Rentable filter is not working fine #2960
Comments
Issue UpdateInvestigation and SolutionI think there are no issues, when you enter your filter in the dashboard, you basically append a new key in the route URL Requests Based on @Omarabdul3ziz two nodes in the second url are on freefarm2 which is a dedicated farm. Does that mean the nodes here are not available for the requested twin? exactly. |
You are right that the "available for" shouldn't be there in that case. |
Is there an existing issue for this?
which package/s did you face the problem with?
Dashboard
What happened?
Used rentable filter to rent a node on quanet with dediacted filter
got this
used dedicated node only got these
used dedicated node and status up got these
i think rentable filter supposed to show any node ready for rent status up or standby
Steps To Reproduce
No response
which network/s did you face the problem on?
QA
version
2.5
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: