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 2020/06/08 05:42:37 UTC
[GitHub] [cloudstack] shwstppr opened a new issue #4133: CKS: Cluster remains in destroying state when non-cluster VMs are using cluster network
shwstppr opened a new issue #4133:
URL: https://github.com/apache/cloudstack/issues/4133
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master 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 -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on master branch.
-->
~~~
4.14.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
N/A
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When additional VMs are added to the k8s cluster network, cluster deletion fails with a message, Unable to delete cluster network. k8s cluster remains in destroying state. It gets removed once non-cluster VMs are migrated from the cluster network. Instead of failing during deletion itself, service can intimate user before deletion that the network is being used by other VMs and they must be migrated before deleting.
##### 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 -->
~~~
1. Create a k8s cluster without passing an existing network.
2. Create and add a new VM to this network outside of CKS
3. Delete k8s cluster
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
Service should throw an error before deleting k8s cluster that cluster network is in use by VMs outside k8s cluster
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Service tries to delete the k8s cluster. Node VMs are deleted. But cannot delete the network. Error is thrown at this time. Cluster shows up in destroying state until VMs are migrated from the network.
~~~
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] rhtyd closed issue #4133: CKS: Cluster remains in destroying state when non-cluster VMs are using cluster network
Posted by GitBox <gi...@apache.org>.
rhtyd closed issue #4133:
URL: https://github.com/apache/cloudstack/issues/4133
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [cloudstack] shwstppr commented on issue #4133: CKS: Cluster remains in destroying state when non-cluster VMs are using cluster network
Posted by GitBox <gi...@apache.org>.
shwstppr commented on issue #4133:
URL: https://github.com/apache/cloudstack/issues/4133#issuecomment-643573864
@PaulAngus @rhtyd please review expected result part. Related to k8s cluster showing in 'Destroying' state issue we discussed briefly.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org