You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2021/07/05 08:35:53 UTC
[GitHub] [cloudstack] vladimirpetrov opened a new issue #5180: Bulk actions: expunge command is ignored when the VMs are already in 'Destroyed' state
vladimirpetrov opened a new issue #5180:
URL: https://github.com/apache/cloudstack/issues/5180
<!--
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.16 main branch
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
N/A
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
N/A
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Expunge command is ignored when the VMs are already in 'Destroyed' state while using the bulk actions.
##### 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 -->
~~~
Steps to reproduce:
1. Deploy one or more VMs.
2. Use bulk actions to destroy them, leaving the 'Expunge' option disabled.
3. Now that the VMs are in 'Destroyed' state, use bulk actions again and this time enable the 'Expunge' option.
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The VMs should be expunged.
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
The VMs are not expunged.
~~~
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] vladimirpetrov closed issue #5180: Bulk actions: expunge command is ignored when the VMs are already in 'Destroyed' state
Posted by GitBox <gi...@apache.org>.
vladimirpetrov closed issue #5180:
URL: https://github.com/apache/cloudstack/issues/5180
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] vladimirpetrov commented on issue #5180: Bulk actions: expunge command is ignored when the VMs are already in 'Destroyed' state
Posted by GitBox <gi...@apache.org>.
vladimirpetrov commented on issue #5180:
URL: https://github.com/apache/cloudstack/issues/5180#issuecomment-875523849
Fix confirmed, closing the issue.
--
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: commits-unsubscribe@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org