configmap "kubesphere-config" not found

[hawking-lab]

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

[pixiake]

The configmap is not created or updated until all components are installed.

You can view the installation progress in ks-installer's log.
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f

[lipengyun066519]

the same problem

[lipengyun066519]

[lipengyun066519]

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.

[lipengyun066519]

accoding to #1090 successed.
kubectl -n kubesphere-system get ValidatingWebhookConfiguration users.iam.kubesphere.io -o yaml >> users.iam.kubesphere.io.yaml
kubectl -n kubesphere-system get secret ks-controller-manager-webhook-cert -o yaml >> ks-controller-manager-webhook-cert.yaml
// edit ca as pr
kubectl -n kubesphere-system apply -f ks-controller-manager-webhook-cert.yaml
kubectl -n kubesphere-system apply -f users.iam.kubesphere.io.yaml

[lipengyun066519]

i finally install kubesphere 3.0.0 in minikube ,k8s'version is 1.9.2.

[escoffier]

I have the same problem.

  Normal   Scheduled    <unknown>             default-scheduler  Successfully assigned kubesphere-system/ks-apiserver-66c548fcd8-nfrcd to node1
  Warning  FailedMount  31h                   kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[ks-router-config kubesphere-config host-time kubesphere-token-p72kq docker-sock]: timed out waiting for the condition
  Warning  FailedMount  30h (x2 over 31h)     kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[kubesphere-config host-time kubesphere-token-p72kq docker-sock ks-router-config]: timed out waiting for the condition
  Warning  FailedMount  30h (x3 over 31h)     kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[kubesphere-token-p72kq docker-sock ks-router-config kubesphere-config host-time]: timed out waiting for the condition
  Warning  FailedMount  30h (x2 over 30h)     kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[host-time kubesphere-token-p72kq docker-sock ks-router-config kubesphere-config]: timed out waiting for the condition
  Warning  FailedMount  30h (x9 over 31h)     kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[docker-sock ks-router-config kubesphere-config host-time kubesphere-token-p72kq]: timed out waiting for the condition
  Warning  FailedMount  30h (x35 over 31h)    kubelet, node1     MountVolume.SetUp failed for volume "kubesphere-config" : configmap "kubesphere-config" not found
  Warning  FailedMount  21m                   kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[docker-sock ks-router-config kubesphere-config host-time kubesphere-token-p72kq]: timed out waiting for the condition
  Warning  FailedMount  12m (x4 over 19m)     kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[kubesphere-config host-time kubesphere-token-p72kq docker-sock ks-router-config]: timed out waiting for the condition
  Warning  FailedMount  9m59s (x2 over 23m)   kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[ks-router-config kubesphere-config host-time kubesphere-token-p72kq docker-sock]: timed out waiting for the condition
  Warning  FailedMount  7m42s (x3 over 28m)   kubelet, node1     Unable to attach or mount volumes: unmounted volumes=[kubesphere-config], unattached volumes=[kubesphere-token-p72kq docker-sock ks-router-config kubesphere-config host-time]: timed out waiting for the condition
  Warning  FailedMount  3m32s (x21 over 30m)  kubelet, node1     MountVolume.SetUp failed for volume "kubesphere-config" : configmap "kubesphere-config" not found

Versions Used:
KubeSphere: v3.0.0
Kubernetes: v1.18.3

[pixiake]

@escoffier
The configmap is not created or updated until all components are installed.

You can view the installation progress in ks-installer's log.
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f

[xiaoshengaimm]

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

[pixiake]

@xiaoshengaimm Is there an error in the log of ks-installer?

[silentbalanceyh]

@pixiake Anyone could reply this issue here. I met the same issue again. The system hung up in ks-installer

**************************************************
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

K8S: 1.25.4 ( 3 nodes: k8s-master, k8s-node-01, k8s-node-02 )
SC:   ceph-csi ( Block Device ) 17.x
The installing mode:  Deploy on K8S with min installing. 

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.
I'm not sure whether the new version missed the kubesphere-config applying ? Could some one help me to investigate this issue here.

[obitoquilt]

same issue