From 62fee495fa832f07021bbe94169fadf698167a06 Mon Sep 17 00:00:00 2001 From: Anirudh9794 Date: Thu, 22 Dec 2022 10:33:19 -0800 Subject: [PATCH] [VCDA-3455] Document known issue - cluster create task running forever due to failure to get API token (#1407) * Document cluster create task running forver when get API token fails as known issue Signed-off-by: Aniruddha Shamasundar * Address review comments Signed-off-by: Aniruddha Shamasundar --- docs/cse3_1/KNOWN_ISSUES.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/cse3_1/KNOWN_ISSUES.md b/docs/cse3_1/KNOWN_ISSUES.md index 4a15679af..4f9fc1c29 100644 --- a/docs/cse3_1/KNOWN_ISSUES.md +++ b/docs/cse3_1/KNOWN_ISSUES.md @@ -234,4 +234,10 @@ to `kubeadm init --config >/path/to/kubeadm.yaml > /root/kubeadm-init.out` Kubernetes version has to be specified within the configuration file itself, -since `--kubernetes-version` and `--config` are incompatible. \ No newline at end of file +since `--kubernetes-version` and `--config` are incompatible. + +### Task for create cluster goes on forever even when cluster create has failed in CSE server +CSE server versions 3.1.1, 3.1.2, 3.1.3 and 3.1.4 are impacted. +This issue will be observed, if the user used to deploy the TKGm kubernetes cluster is missing "Manage user's own API token" right from their role. +The cluster create task will not be marked as "failed" even though CSE server logs will indicate that the cluster creation has failed. +Adding the missing right viz. "Manage user's own API token" to the user's role and reattempting the cluster creation operation should fix the issue.