You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example. api-catalog-deployment.yaml has the following image reference.
image: zowe-docker-snapshot.jfrog.io/ompzowe/api-catalog-services:2.1.1-SNAPSHOT-ubuntu.v2-x-x
I believe this should now be
image: zowe-docker-snapshot.jfrog.io/ompzowe/api-catalog-services:2.18.0-SNAPSHOT-ubuntu.v2-x-x
It appears all of the deployment files are still pointing at 2.1.1 images. They should be updated.
Examine the images in all of the deployment yaml files.
Expected behavior
The deployment files should be pointing to matching image versions for the nightly builds.
Details
Version and build number: zowe-containerization-2.18.0-staging-5795-20240826044410.zip
Willingness to help
If you are willing to help with debugging and reproducing the problem or
with fixing the problem, please state your willingness to assist in the created issue.
Describe the bug
The deployment yaml files in the v2 nightly builds are pointing to the incorrect version of images.
zowe-containerization-2.18.0-staging-5795-20240826044410.zip
For example. api-catalog-deployment.yaml has the following image reference.
image: zowe-docker-snapshot.jfrog.io/ompzowe/api-catalog-services:2.1.1-SNAPSHOT-ubuntu.v2-x-x
I believe this should now be
image: zowe-docker-snapshot.jfrog.io/ompzowe/api-catalog-services:2.18.0-SNAPSHOT-ubuntu.v2-x-x
It appears all of the deployment files are still pointing at 2.1.1 images. They should be updated.
Steps to Reproduce
Expected behavior
The deployment files should be pointing to matching image versions for the nightly builds.
Details
Willingness to help
If you are willing to help with debugging and reproducing the problem or
with fixing the problem, please state your willingness to assist in the created issue.
Yes, willing to help validate fix.
https://github.com/zowe/api-layer/wiki/Issue-management
The text was updated successfully, but these errors were encountered: