-
Notifications
You must be signed in to change notification settings - Fork 750
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configmap "kubesphere-config" not found #907
Comments
The configmap is not created or updated until all components are installed. You can view the installation progress in ks-installer's log. |
the same problem |
becasue my virtualbox's vm mem is too low.after increasing my vm's mem the problem is resolved.but after open kubespere's console ,the error "Internal error occurred: account is not active" occurs. |
accoding to #1090 successed. |
i finally install kubesphere 3.0.0 in minikube ,k8s'version is 1.9.2. |
I have the same problem.
Versions Used: |
@escoffier You can view the installation progress in ks-installer's log. |
The same issue. @pixiake ks-apiserver and ks-controller-manager is dependency on kubesphere-config. They have to mount this config and always containerCreating status. But this config never create. How this solve??? please help |
@xiaoshengaimm Is there an error in the log of ks-installer? |
@pixiake Anyone could reply this issue here. I met the same issue again. The system hung up in **************************************************
Waiting for all tasks to be completed ...
task openpitrix status is successful (1/4)
task network status is successful (2/4)
task multicluster status is successful (3/4)
task monitoring status is failed (4/4)
**************************************************
Collecting installation results ... The pod of ks-apiserver log is as following: Normal Scheduled 9m6s default-scheduler Successfully assigned kubesphere-system/ks-apiserver-5f7b5dcd4c-fjhnr to k8s-node-02
Warning FailedMount 7m3s kubelet Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[kube-api-access-2wftq ks-router-config kubesphere-config host-time]: timed out waiting for the condition
Warning FailedMount 6m58s (x9 over 9m6s) kubelet MountVolume.SetUp failed for volume "kubesphere-config" : configmap "kubesphere-config" not found
Normal Created 4m32s (x3 over 4m55s) kubelet Created container ks-apiserver
Normal Started 4m32s (x3 over 4m55s) kubelet Started container ks-apiserver
Warning BackOff 4m26s (x6 over 4m54s) kubelet Back-off restarting failed container
Normal Pulled 4m2s (x4 over 4m55s) kubelet Container image "kubesphere/ks-apiserver:v3.3.1" already present on machine My Environment
From my testing the SC is working well because I can deploy other pods on the SC here and I could see there is no conflicts between kubesphere and k8s inner source code of ks-installer. |
same issue |
same issue
|
Same issue here |
Events:
Type Reason Age From Message
Normal Scheduled 16m default-scheduler Successfully assigned kubesphere-system/ks-apiserver-7fc9cf7f5-dwbg7 to dev-node-171
Warning FailedMount 7m42s kubelet, dev-node-171 Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[ks-router-config kubesphere-config kubesphere-token-dmwbp docker-sock]: timed out waiting for the condition
Warning FailedMount 5m27s kubelet, dev-node-171 Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[kubesphere-token-dmwbp docker-sock ks-router-config kubesphere-config]: timed out waiting for the condition
Warning FailedMount 52s (x5 over 14m) kubelet, dev-node-171 Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[docker-sock ks-router-config kubesphere-config kubesphere-token-dmwbp]: timed out waiting for the condition
Warning FailedMount 13s (x16 over 16m) kubelet, dev-node-171 MountVolume.SetUp failed for volume "kubesphere-config" : configmap "kubesphere-config" not found
The text was updated successfully, but these errors were encountered: