Failed to ansible-playbook result-info.yaml

[bmmpp]

Describe the Bug

just refer to official doc to install kubesphere3.3 https://kubesphere.io/zh/docs/v3.3/installing-on-kubernetes/introduction/overview/

failed log : "Failed to ansible-playbook result-info.yaml" , Pods status is always 'ContainerCreating' in ‘kubesphere-monitoring-system’ namespaces

for logs below

kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l 'app in (ks-install, ks-installer)' -o jsonpath='{.items[0].metadata.name}') -f

TASK [ks-core/prepare : KubeSphere | Generating kubeconfig-admin] **************
skipping: [localhost]

PLAY RECAP *********************************************************************
localhost                  : ok=29   changed=21   unreachable=0    failed=0    skipped=16   rescued=0    ignored=0
Start installing monitoring
Start installing multicluster
Start installing openpitrix
Start installing network
**************************************************
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 successful  (4/4)
**************************************************
Collecting installation results ...
Failed to ansible-playbook result-info.yaml

For UI issues please also add a screenshot that shows the issue.

Versions Used KubeSphere: 3.3.1 Kubernetes: 1.24.8

Environment How many nodes and their hardware configuration:

For example: Rocky9.1 / 3 masters: 4cpu/8g; 3 nodes: 2cpu/2g (and other info are welcomed to help us debugging)

How To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

[nitendra-thakur]

Any update on this? I'm facing the same issue.

[bmmpp]

Any update on this? I'm facing the same issue.

waiting a long time, It's ready.

[clouddea]

I' m facing this issue to...

[Imccccc]

any update?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.