shwstppr opened a new issue #4107:
URL: https://github.com/apache/cloudstack/issues/4107
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Bug Report
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
CKS
~~~
##### 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
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When CKS is set to use a CoreOS template with a name which is same as an
already deleted template, plugin fails to deploy Kubernetes clusters using new,
active template
##### 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. Enable CKS plugin
2. Register CoreOS template
3. Delete that template after installation
4. Add the template again with the same name
5. Change the cloud.kubernetes.cluster.template.name.* with the template
name
6. Verify template is successfully installed
7. Register Kubernetes version ISO and try to deploy a 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? -->
~~~
Cluster should be deployed successfully using recently registered, active
CoreOS template
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
Cluster deployment fails,
2020-05-27 09:03:55,080 DEBUG [c.c.a.ApiServlet]
(qtp1104443373-22:ctx-610114b3) (logid:3f96511a) ===START=== 10.1.0.1 -- GET
command=createKubernetesCluster&response=json&name=K8s-cluster1&description=K8s-cluster1&zoneid=6c099729-4848-4165-bb30-53764af7a245&kubernetesversionid=fc6953b6-c1e7-49f1-81be-2661c804e059&serviceofferingid=e377c887-b5e9-41e6-851b-ea7f37115ee3&size=3&keypair=&masternodes=1&_=1590568220199
2020-05-27 09:03:55,084 DEBUG [c.c.a.ApiServer]
(qtp1104443373-22:ctx-610114b3 ctx-294f0797) (logid:3f96511a) CIDRs from which
account 'Acct[18042dac-9c0b-11ea-8607-1e004f01080f-admin]' is allowed to
perform API calls: 0.0.0.0/0,::/0
2020-05-27 09:03:55,090 WARN [c.c.k.c.KubernetesClusterManagerImpl]
(qtp1104443373-22:ctx-610114b3 ctx-294f0797) (logid:3f96511a) The template ID:
199c5101-cbbb-481a-8319-7d06329d7461, name: coreos-kvm is not available for use
in zone ID: 6c099729-4848-4165-bb30-53764af7a245 provisioning Kubernetes
cluster nodes
2020-05-27 09:03:55,090 INFO [c.c.a.ApiServer]
(qtp1104443373-22:ctx-610114b3 ctx-294f0797) (logid:3f96511a) Kubernetes
service has not been configured properly to provision Kubernetes clusters
2020-05-27 09:03:55,090 DEBUG [c.c.a.ApiServlet]
(qtp1104443373-22:ctx-610114b3 ctx-294f0797) (logid:3f96511a) ===END===
10.1.0.1 -- GET
command=createKubernetesCluster&response=json&name=K8s-cluster1&description=K8s-cluster1&zoneid=6c099729-4848-4165-bb30-53764af7a245&kubernetesversionid=fc6953b6-c1e7-49f1-81be-2661c804e059&serviceofferingid=e377c887-b5e9-41e6-851b-ea7f37115ee3&size=3&keypair=&masternodes=1&_=1590568220199
~~~
----------------------------------------------------------------
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:
[email protected]
