govc returned error when logging out from session without cert verification
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
My management cluster is successfully created. However, govc reports error at the end
"error": "govc returned error when logging out from session without cert verification: govc: ServerFaultCode: Cannot complete login due to an incorrect user name or password.\n"}
My eks anywhere version is 0.11.3
And in the YAML file I have the correct thumbprint and insecure set to True (note: if I set insecure to False, the cluster creation fails)
EMPHASIS IS THAT WHILE CLUSTER IS SUCCESSFULLY CREATED, govc does not logout and stale docker containers of bootstrap cluster remain forever on the Admin machine unless manually deleted.
Installing GitOps Toolkit on workload cluster
GitOps field not specified, bootstrap flux skipped
Writing cluster config file
Deleting bootstrap cluster
🎉 Cluster created!
--------------------------------------------------------------------------------------
The Amazon EKS Anywhere Curated Packages are only available to customers with the
Amazon EKS Anywhere Enterprise Subscription
--------------------------------------------------------------------------------------
Installing curated packages controller on management cluster
Installing helm chart on cluster {"chart": "eks-anywhere-packages", "version": "0.2.7-eks-a-17"}
Warning: No AWS key/license provided. Please be aware this will prevent the package controller from installing curated packages.
job.batch/eksa-auth-refresher created
Closer failed {"closerType": "*dependencies.Dependencies", "error": "govc returned error when logging out from session without cert verification: govc: ServerFaultCode: Cannot complete login due to an incorrect user name or password.\n"}
Contributor guide
Research direction
Start by reproducing the EKS Anywhere 0.11.3 cluster-creation workflow with insecure set to True and inspect the govc logout cleanup path after the bootstrap cluster is deleted. Done means cluster creation still succeeds, logout does not report an authentication error, and stale bootstrap Docker containers are removed automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100