We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Issue: when creating a plan using wizard and choosing a provider with no vms, vm table gets stuck on loading
how to reproduce: a. create a source provider with no vms b. use "create plan wizard" and choose this empty source provider
what happen: vm list is stuck on loading
what should happen: vm list should say "no vms"
Screenshot:
The text was updated successfully, but these errors were encountered:
addressed by #1237
Sorry, something went wrong.
yaacov
No branches or pull requests
Issue:
when creating a plan using wizard and choosing a provider with no vms, vm table gets stuck on loading
how to reproduce:
a. create a source provider with no vms
b. use "create plan wizard" and choose this empty source provider
what happen:
vm list is stuck on loading
what should happen:
vm list should say "no vms"
Screenshot:
![vm-list-loading](https://private-user-images.githubusercontent.com/2181522/342678858-2c98c874-201a-402c-b99f-3c71e6f45cb8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2NDkwNDAsIm5iZiI6MTczOTY0ODc0MCwicGF0aCI6Ii8yMTgxNTIyLzM0MjY3ODg1OC0yYzk4Yzg3NC0yMDFhLTQwMmMtYjk5Zi0zYzcxZTZmNDVjYjgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTVUMTk0NTQwWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MTUwYTU5MzQ0MjZkMmY0Yzg2MmNhZTY5ZjZiMzM4NDYzMDFhNmI4OWNlNjJhYzgwOGEyMjA0NGQxMmZiYTY5MyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.-fzela6SXQ7tIhJUyTtu_XNddqEHXeTKolM6ucBnKdc)
The text was updated successfully, but these errors were encountered: