My deploy is getting an ErrImagePull error when trying to copy and deploy a project to a non-default region.
I have a small new cluster that has two regions. One region is "default" and the other is our performance testing region. A project I created in the performance testing region fails with ErrImagePull when deploying.
This is what I have done:
I built a development project in the default region. It has a successfully building and deploying application in it.
I created 3 new empty projects in an attempt to copy the original project. My goal is to have multiple copies of the same project for a deployment pipeline.
I recreated the bc, dc, src, and routes by exporting from the development project and using "oc create" in the new projects to make the objects.
Two of these three new projects use the default node-selector, while the third project has a non-standard node selector in the namespace definition.
I used the "oc tag" command to create an image stream that uses the same image as the development project.
- oc tag originalproject/vault:latest
oc tag originalproject/vault:latest copyproject2/vault:latest
oc tag originalproject/vault:latest performancetestingproject/vault:latest
- This works fine in the projects that are set to the default region, but not on the project that is in the performance testing region. I can see that the
pods build on the right node, but that node does not appear to have the images or tags shown in the "docker images" output.
Surely I am doing something simple incorrectly. I may not be understanding the proper way to use "tag" or how images work within openshift.
Thanks for any help you can provide.
Senior Unix Administrator, Infrastructure
Availity | 10752 Deerwood Park Blvd S. Ste 110, Jacksonville FL 32256
W 904.470.4953 | M 561.313.2866
Gary Franczyk availity com
The information contained in this e-mail may be privileged and confidential under applicable law. It is intended solely for the use of the person or firm named above. If the reader of this e-mail is not the intended recipient, please notify us immediately by returning the e-mail to the originating e-mail address. Availity, LLC is not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Availity, LLC.