安装后,点应用商店报错,错误信息如下:

tzghost 测试openpitrix-isv-manager.openpitrix-system.svc:9118正常

/ # nc -zv openpitrix-isv-manager.openpitrix-system.svc 9118
openpitrix-isv-manager.openpitrix-system.svc (10.233.16.29:9118) open
/ #

    tzghost 对应的POD
    [root@node1 ~]# kubectl -n openpitrix-system get job
    NAME COMPLETIONS DURATION AGE
    hyperpitrix-release-app-job 1/1 23m 3d1h
    openpitrix-app-db-ctrl-job 0/1 139m 139m
    openpitrix-attachment-db-ctrl-job 1/1 8m40s 3d1h
    openpitrix-cluster-db-ctrl-job 1/1 6s 139m
    openpitrix-db-init-job 1/1 4s 140m
    openpitrix-isv-db-ctrl-job 1/1 7m59s 3d1h
    openpitrix-job-db-ctrl-job 1/1 8m11s 3d1h
    openpitrix-repo-db-ctrl-job 1/1 8m44s 3d1h
    openpitrix-runtime-db-ctrl-job 1/1 9m13s 3d1h
    openpitrix-task-db-ctrl-job 1/1 9m18s 3d1h
    [root@node1 ~]#
    [root@node1 ~]#
    [root@node1 ~]# kubectl -n openpitrix-system get pod
    NAME READY STATUS RESTARTS AGE
    hyperpitrix-release-app-job-jvkvt 0/1 Completed 0 3d1h
    openpitrix-attachment-db-ctrl-job-wcmlm 0/1 Completed 5 3d1h
    openpitrix-cluster-db-ctrl-job-mxgjj 0/1 Completed 0 153m
    openpitrix-db-init-job-f2wtv 0/1 Completed 0 154m
    openpitrix-hyperpitrix-deployment-dddd548bd-99wxr 1/1 Running 0 3d1h
    openpitrix-isv-db-ctrl-job-8r64p 0/1 Completed 4 3d1h
    openpitrix-job-db-ctrl-job-g69dx 0/1 Completed 5 3d1h
    openpitrix-repo-db-ctrl-job-fzrqg 0/1 Completed 4 3d1h
    openpitrix-rp-kubernetes-deployment-5cdf9c56c8-x8b2b 1/1 Running 0 3d1h
    openpitrix-runtime-db-ctrl-job-7x8nv 0/1 Completed 5 3d1h
    openpitrix-task-db-ctrl-job-f5rw9 0/1 Completed 5 3d1h
    [root@node1 ~]#

      tzghost openpitrix-app-db-ctrl-job这个job没有执行成功,执行一下这个命令
      kubectl -n openpitrix-system get job openpitrix-app-db-ctrl-job -o json | jq ‘del(.spec.selector)’ | jq ‘del(.spec.template.metadata.labels)’ | kubectl replace –force -f -

        wanjunlei 如下报错
        [root@node1 ~]# kubectl -n openpitrix-system get pod
        NAME READY STATUS RESTARTS AGE
        hyperpitrix-release-app-job-jvkvt 0/1 Completed 0 3d18h
        openpitrix-app-db-ctrl-job-vs2tj 0/1 CrashLoopBackOff 5 4m19s
        openpitrix-attachment-db-ctrl-job-wcmlm 0/1 Completed 5 3d18h
        openpitrix-cluster-db-ctrl-job-mxgjj 0/1 Completed 0 18h
        openpitrix-db-init-job-f2wtv 0/1 Completed 0 18h
        openpitrix-hyperpitrix-deployment-dddd548bd-99wxr 1/1 Running 0 3d18h
        openpitrix-isv-db-ctrl-job-8r64p 0/1 Completed 4 3d18h
        openpitrix-job-db-ctrl-job-g69dx 0/1 Completed 5 3d18h
        openpitrix-repo-db-ctrl-job-fzrqg 0/1 Completed 4 3d18h
        openpitrix-rp-kubernetes-deployment-5cdf9c56c8-x8b2b 1/1 Running 0 3d18h
        openpitrix-runtime-db-ctrl-job-7x8nv 0/1 Completed 5 3d18h
        openpitrix-task-db-ctrl-job-f5rw9 0/1 Completed 5 3d18h

        tzghost 执行下面这个命令看看

        kubectl exec -it -n kubesphere-system `kubectl get pod -n kubesphere-system | grep mysql | awk '{print $1}'` -- sh -c 'mysql -uroot -ppassword -e "select * from app.flyway_schema_history";'

          先删app库

          kubectl exec -it -n kubesphere-system `kubectl get pod -n kubesphere-system | grep mysql | awk '{print $1}'` -- sh -c 'mysql -uroot -ppassword -e "drop database app";'

          然后重新执行job:

          kubectl -n openpitrix-system get job openpitrix-app-db-ctrl-job -o json | jq ‘del(.spec.selector)’ | jq ‘del(.spec.template.metadata.labels)’ | kubectl replace –force -f -

            tzghost

            kubectl -n openpitrix-system get job openpitrix-db-init-job -o json | jq ‘del(.spec.selector)’ | jq ‘del(.spec.template.metadata.labels)’ | kubectl replace –force -f -

            complete之后执行下面

            kubectl -n openpitrix-system get job openpitrix-app-db-ctrl-job -o json | jq ‘del(.spec.selector)’ | jq ‘del(.spec.template.metadata.labels)’ | kubectl replace –force -f -

              tzghost

              kubectl -n openpitrix-system get job hyperpitrix-release-app-job -o json | jq ‘del(.spec.selector)’ | jq ‘del(.spec.template.metadata.labels)’ | kubectl replace –force -f -
                4 个月 后

                我的和上述情况都不太一样,job只有一个,有时好用,有时不好用,下面是在不好用的情况下查询的job应该怎么解决呢?

                / # kubectl get job -n openpitrix-system
                NAME                          COMPLETIONS   DURATION   AGE
                hyperpitrix-release-app-job   1/1           57s        21d