hetao runzexia 我的也是,centos 7.5 nfs存储,然后helm为2.14.3,安装2.1版本ks;试了两次都报错,卡的有点久了

helm del --purge ks-minio
kubectl get pod ks-installer-7987c659d6-sg8pv -n kubesphere-system -o yaml | kubectl replace --force -f -
TASK [common : Kubesphere | Deploy minio] **************************************

fatal: [localhost]: FAILED! => {"changed": true, "cmd": "/usr/local/bin/helm upgrade --install ks-minio /etc/kubesphere/minio-ha -f /etc/kubesphere/custom-values-minio.yaml --set fullnameOverride=minio --namespace kubesphere-system --wait --timeout 1800\n", "delta": "0:30:01.145146", "end": "2019-12-04 02:43:29.052773", "msg": "non-zero return code", "rc": 1, "start": "2019-12-04 02:13:27.907627", "stderr": "Error: release ks-minio failed: timed out waiting for the condition", "stderr_lines": ["Error: release ks-minio failed: timed out waiting for the condition"], "stdout": "Release \"ks-minio\" does not exist. Installing it now.", "stdout_lines": ["Release \"ks-minio\" doesnot exist. Installing it now."]}
...ignoring

TASK [common : debug] **********************************************************
ok: [localhost] => {
    "msg": [
        "1. check the storage configuration and storage server",
        "2. execute 'helm del --purge ks-minio'",
        "3. Restart the installer pod in kubesphere-system namespace"
    ]
}

TASK [common : fail] ***********************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "It is suggested to refer to the above methods for troubleshooting problems ."}

PLAY RECAP *********************************************************************
localhost                  : ok=24   changed=18   unreachable=0    failed=1    skipped=66   rescued=0    ignored=1

    rysinal

    1. 首先删除 minio helm del --purge ks-minio
    2. 进入installer pod bash kubectl exec -n kubesphere-system ks-installer-xx -it sh
    3. 执行minio 安装命令 /usr/local/bin/helm upgrade --install ks-minio /etc/kubesphere/minio-ha -f /etc/kubesphere/custom-values-minio.yaml --set fullnameOverride=minio --namespace kubesphere-system --wait --timeout 1800
    4. 观察minio状态,排查为何出错

      runzexia

      [root@master ~]# helm del --purge ks-minio
      release "ks-minio" deleted
      [root@master ~]# kubectl get pods -n kubesphere-system
      NAME                            READY   STATUS    RESTARTS   AGE
      ks-installer-7987c659d6-rp9px   1/1     Running   0          40m
      minio-make-bucket-job-rl9bw     1/1     Running   1          38m
      openldap-0                      1/1     Running   0          14h
      redis-5d4844b947-gzbsh          1/1     Running   0          14h
      [root@master ~]# kubectl exec -n kubesphere-system ks-installer-7987c659d6-rp9px -it sh
      / # /usr/local/bin/helm upgrade --install ks-minio /etc/kubesphere/minio-ha -f /etc/kubesphere/custom-values-minio.yaml --set fullnameOverride=minio --namespace kubesphere
      -system --wait --timeout 1800
      Release "ks-minio" does not exist. Installing it now.
      Error: jobs.batch "minio-make-bucket-job" already exists
      / #

        rysinal

        Events:
          Type     Reason       Age                From               Message
          ----     ------       ----               ----               -------
          Normal   Scheduled    50m                default-scheduler  Successfully assigned kubesphere-system/minio-make-bucket-job-rl9bw to node2
          Normal   Pulling      50m                kubelet, node2     Pulling image "minio/mc:RELEASE.2019-08-07T23-14-43Z"
          Normal   Pulled       49m                kubelet, node2     Successfully pulled image "minio/mc:RELEASE.2019-08-07T23-14-43Z"
          Normal   Created      11m (x3 over 49m)  kubelet, node2     Created container minio-mc
          Normal   Started      11m (x3 over 49m)  kubelet, node2     Started container minio-mc
          Normal   Pulled       11m (x2 over 30m)  kubelet, node2     Container image "minio/mc:RELEASE.2019-08-07T23-14-43Z" already present on machine
          Warning  FailedMount  1s (x12 over 11m)  kubelet, node2     MountVolume.SetUp failed for volume "minio-configuration" : [configmap "minio" not found, secret "minio" notfound]

        看日志是存储问题,现在在每个节点安装了yum install -y nfs-utils
        runzexia 大佬,现在报错为新的

        TASK [common : Kubesphere | Deploy minio] **************************************
        fatal: [localhost]: FAILED! => {"changed": true, "cmd": "/usr/local/bin/helm upgrade --install ks-minio /etc/kubesphere/minio-ha -f /etc/kubesphere/custom-values-minio.yaml --set fullnameOverride=minio --namespace kubesphere-system --wait --timeout 1800\n", "delta": "0:00:23.077751", "end": "2019-12-04 05:10:12.887874", "msg": "non-zero return code", "rc": 1, "start": "2019-12-04 05:09:49.810123", "stderr": "Error: jobs.batch \"minio-make-bucket-job\" already exists", "stderr_lines": ["Error: jobs.batch \"minio-make-bucket-job\" already exists"], "stdout": "Release \"ks-minio\" does not exist. Installing it now.", "stdout_lines": ["Release \"ks-minio\" does not exist. Installing it now."]}

        删除了minio 的deveop和pod,包括job的pod,然后重新安装也是这样报错

        kubectl delete deployment minio -n kubesphere-system
        kubectl delete pod minio-8cd46c8d9-287gw -n kubesphere-system
        kubectl delete pod minio-make-bucket-job-mvtzz -n kubesphere-system
        helm del --purge ks-minio
        kubectl get pod ks-installer-7987c659d6-ttprq -n kubesphere-system -o yaml | kubectl replace --force -f -

          rysinal 更改calio为flannel 一般都是因为底层网络不支持ipip协议影响k8s集群的dns解析所造成的

            7 天 后

            rysinal 查看一下异常的pod,describe或者看一下pod的日志,我失败的原因是写错了nfs的挂载目录

            4 个月 后
            15 天 后

            BoBo-G 更改calio为flannel 一般都是因为底层网络不支持ipip协议影响k8s集群的dns解析所造成的

            看到有这样解决的,但是calico已经部署好了,还有其他解决办法么

            2 个月 后

            rysinal
            我也遇到这个问题,minio始终安装失败,请问你用的是离线安装吗,在线安装没有找到 kube_network_plugin: flannel的配置。

            1 年 后
            17 天 后

            rysinal 这个文件在哪找啊bro,不知道在哪更改这个。我也是安装日志到deploy minio就不动了

              2 个月 后

              v1.21.2 3.1.0 安装也是报这样的错误