andrijapanicsb opened a new issue, #7840:
URL: https://github.com/apache/cloudstack/issues/7840
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
UI
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.17.2
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
No special configuration needed.
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
NA
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Start VM deployment process and leave the VM being deployed (it takes 5+
seconds)
Go immediately and list e.g. single VPC details (chose VPC and click on it),
wait for a bit until the previous API call (to deploy VM) is completed, and the
current view (a specific VPC view) will be replaced with the VM view (the VM
which you have deployed).
This is not critical.
However, a user searching for VM (many results, so all API calls in
background take time to complete), then quickly clicking the VM, clicking the
delete button - can result in user deleting the wrong VM - see the video
demonstraion here: https://screenpal.com/watch/c0j6j7VkPJC
**DUE TO THIS, I MARK IT AS CRITICAL.**
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
<!-- Paste example playbooks or commands between quotes below -->
~~~
See the Summary above, see the video.
Beside fixing the "refresh of UI after previous API call completion" general
problem - it's critical to reproduce the deletion bug issue, to be able to
confirm it is fixed later and not rely on general fix and hope it fixes the
deletion issue.
I assume that introducing additional latency (Chrome can do this in
Developer Tools) will help make sure that API calls takes long time to
complete, so it should be doable to reproduce the issue (I'm still working on
reproducing the deletion bug)
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
~~~
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
