Open kiranchavala opened 4 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/kind bug
What steps did you take and what happened:
export CLOUDSTACK_TEMPLATE_NAME=ubuntu-2004-kube-v1.27.2-kvm
What did you expect to happen:
Capc Cluster should get created successfully
Expected behaviour Anything else you would like to add:
When you execute the cloudstack list template API call with user credentials capc should give importance to the template which is registered by the user
https://cloudstack.apache.org/api/apidocs-4.19/apis/listTemplates.html
Environment:
Cloudstack version : 4.19