StepBee opened a new issue, #6657:
URL: https://github.com/apache/cloudstack/issues/6657
<!--
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.
-->
~~~
Kubernetes, CKS, KubernetesClusterManagerImpl
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.17.0.1
~~~
##### 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
-->
KVM based hypervisor
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Creating a Kubernetes Cluster fails with error message "Creating Kubernetes
cluster failed due to insufficient capacity" when the Service Offering has more
than one host tag, comma separated.
##### 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.
-->
1. If no host with more than one host tag exists, assign one or more hosts
more than one host tag, comma separated, for example
performance,nowindows
2. If not existing yet, create a Kubernetes ISO with min CPU 2 and min
Memory 2048 MB
3. Create a Service Offering with multiple host tags, matching the host tags
of the first step, in our example
performance,nowindows
and which is fitting the minimum kubernetes requirements of step two, in our
example more than 2 vCPU and more than 2048 MB Memory
4. Chose "Compute / Kubernetes / Create Kubernetes Cluster" and select the
Compute Offering with more than one host tag, created earlier.
The deployment will fail with the error message
"Request failed. (530) Creating Kubernetes cluster failed due to
insufficient capacity for 2 nodes cluster in zone : xxxx with service offering
xxxx"
The management server log will show
```
2022-08-18 17:34:06,835 DEBUG [c.c.u.AccountManagerImpl]
(qtp262366552-3231:ctx-aaf26d13 ctx-13c55a78) (logid:6ff75d8d) Access to
Acct[xxxxxxx-xxxxxxx] -- Account {"id":
60, "name": "xxxxxxx", "uuid": "xxxxxxx"} granted to Acct[xxxxxxx-xxxxxxx]
-- Account {"id": 60, "name": "xxxxxxx", "uuid": "xxxxxxxxxx"} by DomainChecker
2022-08-18 17:34:06,958 INFO [c.c.k.c.KubernetesClusterManagerImpl]
(qtp262366552-3231:ctx-aaf26d13 ctx-13c55a78) (logid:6ff75d8d) Suitable hosts
not found in datacenter ID: f2665eef-1073-4c50-8d3a-076d4
4036fcc for node 1 with offering ID: 1b2c036e-d7c6-470e-820c-83b34f8d5af7
2022-08-18 17:34:06,958 WARN [c.c.k.c.KubernetesClusterManagerImpl]
(qtp262366552-3231:ctx-aaf26d13 ctx-13c55a78) (logid:6ff75d8d) Cannot find
enough capacity for Kubernetes cluster(requested cpu=8000 me
mory=8589934592) with offering ID: 1b2c036e-d7c6-470e-820c-83b34f8d5af7
2022-08-18 17:34:06,959 ERROR [c.c.k.c.KubernetesClusterManagerImpl]
(qtp262366552-3231:ctx-aaf26d13 ctx-13c55a78) (logid:6ff75d8d) Creating
Kubernetes cluster failed due to insufficient capacity for 2 no
des cluster in zone : Zone-01 with service offering : Medium
2022-08-18 17:34:06,959 INFO [c.c.a.ApiServer]
(qtp262366552-3231:ctx-aaf26d13 ctx-13c55a78) (logid:6ff75d8d) Creating
Kubernetes cluster failed due to insufficient capacity for 2 nodes cluster in
zone :
Zone-01 with service offering : Medium
2022-08-18 17:34:06,961 DEBUG [c.c.a.ApiServlet]
(qtp262366552-3231:ctx-aaf26d13 ctx-13c55a78) (logid:6ff75d8d) ===END===
79.205.55.140 -- GET
name=test-kube-01&description=test-kube-01&zoneid=f2665eef-1073
-4c50-8d3a-076d44036fcc&kubernetesversionid=764c7c5a-f08b-48ad-9a0a-da4924030fc3&serviceofferingid=1b2c036e-d7c6-470e-820c-83b34f8d5af7&size=1&noderootdisksize=8&keypair=ssh-key-ed25519&command=create
KubernetesCluster&response=json
```
The log clearly shows it's not a capacity issue, it's not even checking a
single hosts capacity, because no host is found suitable in the cluster.
Using exactly the same Service Offering to create a normal instance works
fine.
Using a Service Offering with none or one host tag assigned to create a
Kubernetes Cluster works fine.
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
As with normal instances, creating a kubernetes cluster should work with
service offerings, which have more than 2 host tags comma separated assigned,
as well.
##### ACTUAL RESULTS
<!-- What actually happened? -->
Creating the Kubernetes Cluster fails with the error message
<!-- Paste verbatim command output between quotes below -->
~~~
"Request failed. (530) Creating Kubernetes cluster failed due to
insufficient capacity for 2 nodes cluster in zone : xxxx with service offering
xxxx"
~~~
--
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]
