Solved

Error: ErrImagePull-calico-node

  • 16 April 2023
  • 5 replies
  • 314 views

Userlevel 6
Badge +14

Hi

I am receiving the below error during it created pods(after running the main script).

 

 

 

 

 

 

  Warning  Failed     <invalid> (x3 over <invalid>)   kubelet            Failed to pull image "ifscloud.jfrog.io/docker/calico/node:v3.19.1": rpc error: code = Unknown desc = failed to pull and unpack image "ifscloud.jfrog.io/docker/calico/node:v3.19.1": failed to copy: httpReadSeeker: failed open: unexpected status code https://ifscloud.jfrog.io/v2/docker/calico/node/manifests/sha256:bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55: 403 Forbidden - Server message: unknown: Rejected artifact download request: User ale-pyqol8y is not permitted to deploy 'calico/node/sha256__bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55/list.manifest.json' into 'docker-hub-cache:calico/node/sha256__bc4a631d553b38fdc169ea4cb8027fa894a656e80d68d513359a4b9d46836b55/list.manifest.json'.
 
 Warning  Failed     <invalid> (x3 over <invalid>)   kubelet            Error: ErrImagePull
 
 Warning  Failed     <invalid> (x3 over <invalid>)   kubelet            Error: ImagePullBackOff
  
Normal   BackOff    <invalid> (x72 over <invalid>)  kubelet            Back-off pulling image "ifscloud.jfrog.io/docker/calico/node:v3.19.1"

 

 

 

Please note

We are using the OVM image downloaded from the build place

 



 

icon

Best answer by Charith Epitawatta 28 April 2023, 13:07

View original

5 replies

Userlevel 6
Badge +14

@Charith Epitawatta 

Userlevel 5
Badge +10

Is the password wrong on user ale-pyqol8y?  You get a “not permitted to deploy”, i guess you should get a authorization error, but for future reference :)

If the password has special characters it need to be quoted in the ifscloud-values.yaml

e.g.
  imageCredentials:
    username: ale-pyqol8y
    password: #ANlXYp+d4=#

More likely It can be a problem with connection to ifscloud.jfrog.io. The k8s DNS might be malconfigured - read the remote installation documentations on how to set DNS to the customers internal DNS server.
https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/030_preparing_server/50_windows_managementserver/#set_coredns_dns_server

It can also be that the customer network requires all outbound traffic to be proxied - also described in the techdoc https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/030_preparing_server/60_install_behind_proxy/

 

Userlevel 6
Badge +14

Is the password wrong on user ale-pyqol8y?  You get a “not permitted to deploy”, i guess you should get a authorization error, but for future reference :)

If the password has special characters it need to be quoted in the ifscloud-values.yaml

e.g.
  imageCredentials:
    username: ale-pyqol8y
    password: #ANlXYp+d4=#

More likely It can be a problem with connection to ifscloud.jfrog.io. The k8s DNS might be malconfigured - read the remote installation documentations on how to set DNS to the customers internal DNS server.
https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/030_preparing_server/50_windows_managementserver/#set_coredns_dns_server

It can also be that the customer network requires all outbound traffic to be proxied - also described in the techdoc https://docs.ifs.com/techdocs/23r1/070_remote_deploy/010_installing_fresh_system/030_preparing_server/60_install_behind_proxy/

 

Thank you very much for your reply. Below are some aditional information.

The issue is after running the main script

 

Userlevel 7
Badge +31

Hi @Darshana Herath,

Sorry about the late response. This issue occurs because the JFrog Artifactory user does not have “Deploy/cache” privileges. We have had a similar issue reported by a customer and it was resolved by adding these permissions. Please open a case if the issue still exists. 

Hope this helps!

Userlevel 6
Badge +14

Hi @Darshana Herath,

Sorry about the late response. This issue occurs because the JFrog Artifactory user does not have “Deploy/cache” privileges. We have had a similar issue reported by a customer and it was resolved by adding these permissions. Please open a case if the issue still exists. 

Hope this helps!

Thank you Charith, Yes That case is mine.

Reply