Getting ImagePullBackoff issue during Quick installation of Spaceone

[varunmanju]

Am getting an ImagePullBackOff issue during the quick installation of Cloudforet using MiniKube. it arises when trying to pull the deploy the console-api and dashboard pod. Tried using different versions of the software but the same issue arises.Any way to resolve this issue?

[varunmanju]

[varunmanju]

I get the following error when i describe the pod console-api-v2-rest-5c6bd958d7-gqp7z.

  Type     Reason       Age                    From               Message
  ----     ------       ----                   ----               -------
  Normal   Scheduled    2m31s                  default-scheduler  Successfully assigned spaceone/console-api-v2-rest-5c6bd958d7-gqp7z to minikube
  Warning  FailedMount  2m19s (x2 over 2m20s)  kubelet            MountVolume.SetUp failed for volume "shared-conf" : failed to sync configmap cache: timed out waiting for the condition
  Normal   Pulled       2m9s                   kubelet            Container image "nginx:stable" already present on machine
  Normal   Created      2m9s                   kubelet            Created container console-api-v2-nginx
  Normal   Started      2m8s                   kubelet            Started container console-api-v2-nginx
  Normal   Pulling      82s (x3 over 2m11s)    kubelet            Pulling image "spaceone/console-api-v2:latest"
  Warning  Failed       81s (x3 over 2m9s)     kubelet            Failed to pull image "spaceone/console-api-v2:latest": rpc error: code = Unknown desc = Error response from daemon: manifest for spaceone/console-api-v2:latest not found: manifest unknown: manifest unknown
  Warning  Failed       81s (x3 over 2m9s)     kubelet            Error: ErrImagePull
  Warning  Failed       54s (x5 over 2m4s)     kubelet            Error: ImagePullBackOff
  Normal   BackOff      43s (x6 over 2m4s)     kubelet            Back-off pulling image "spaceone/console-api-v2:latest"

For dashboard-698d9cb488-rr8cc i get the same error.

[choonho]

There is version problem with helm chart and value.yaml.
Your helm chart version may be spaceone-1.10.5 like

choonhoson v1.10.4 %> helm list
NAME    	NAMESPACE	REVISION	UPDATED                             	STATUS	CHART          	APP VERSION
spaceone	default  	1       	2023-01-19 17:31:04.120809 +0900 KST	failed	spaceone-1.10.5	1.10.4

So instead of using v1.9.4 example, use charts/examples/v1.10.4

cd charts/examples/v1.10.4
helm install spaceone -f minikube.yaml spaceone/spaceone

[GeunjeLEE]

Hi @varunmanju !
Thank your for you reporting.

We will update the example values ​​to fix this issue and inform you soon.

thank you.

[GeunjeLEE]

Hi @varunmanju

We have been updated example, please reinstall with v1.10.4 value.
(Alternatively, copy over the old minikube.yaml and upgrade your helm release.)

• All image versions of examples have been updated..
• console-api-v2-rest-**** and dashboard-**** pods will no longer appear because these two pads are not for release.

[varunmanju]

NAME                                                    READY   STATUS             RESTARTS      AGE
board-dd6bbcc6f-dcz5v                                   1/1     Running            0             20m
config-5b5fbc7b46-pgscl                                 1/1     Running            0             20m
console-777f764fb4-bvfcb                                0/1     ImagePullBackOff   0             20m
console-api-54fc6c7f8b-f264b                            2/2     Running            0             22m
file-manager-6fc76cfbf5-bdvw2                           1/1     Running            0             20m
identity-568f449cbc-mjdzd                               1/1     Running            0             22m
initialize-spaceone-kdhfw-9q9wz                         0/1     Init:0/2           0             20m
inventory-86686bd684-xv64d                              1/1     Running            0             20m
inventory-scheduler-58d6fcfd8f-zgbbx                    1/1     Running            0             20m
inventory-worker-5bbd45899c-pzvql                       1/1     Running            0             20m
mongodb-599d9897d8-mb7rm                                1/1     Running            0             20m
monitoring-58ffb4d598-t28ss                             0/1     ImagePullBackOff   0             20m
notification-5965b5c496-tzmb8                           1/1     Running            0             20m
notification-scheduler-97f65cf46-c2j5l                  1/1     Running            0             22m
notification-worker-7c64579f44-bfvx9                    1/1     Running            0             20m
plugin-789f977c89-9rhbr                                 1/1     Running            0             20m
redis-5b7455bcf6-4sbsc                                  1/1     Running            0             20m
repository-765bff7c7b-ls4rl                             1/1     Running            0             20m
secret-79b69db87c-p6v8r                                 0/1     ImagePullBackOff   0             20m
spaceone-consul-connect-injector-5584bd44f-lgr74        1/1     Running            2 (11m ago)   22m
spaceone-consul-server-0                                1/1     Running            0             22m
spaceone-consul-webhook-cert-manager-559ddb994f-gnbhr   1/1     Running            0             22m
statistics-88ff7fcf-qhn8c                               1/1     Running            0             22m

[varunmanju]

getting this ImagePullBackoff for console-777f764fb4-bvfcb, monitoring-58ffb4d598-t28ss , secret-79b69db87c-p6v8r in version 1.10.4

[GeunjeLEE]

hi @varunmanju

Could you please share kubectl describe {pod_name} logs so that we can find the cause of the problem?

[varunmanju]

it worked now.For some strange reason.

[GeunjeLEE]

It's nice to know that the pod is working :)

Please open a discussion if you encounter any other issues.
Thank you.