Description of problem: These four images are not latest on registry.access.stage.redhat.com and registry.access.redhat.com: jenkins-1-rhel7 jenkins-2-rhel7 jenkins-slave-maven-rhel7 jenkins-slave-nodejs-rhel7 Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Check these four images in registry.access.stage.redhat.com and registry.access.redhat.com: jenkins-1-rhel7 jenkins-2-rhel7 jenkins-slave-maven-rhel7 jenkins-slave-nodejs-rhel7 Actual results: These four images are not latest and have no v3.5 tag. Expected results: They should be pushed with latest image and have v3.5 tag. Additional info: For example: # curl -X GET -k registry.access.redhat.com/v1/repositories/openshift3/jenkins-2-rhel7/tags | python -m json.tool 2>/dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 768 100 768 0 0 4005 0 --:--:-- --:--:-- --:--:-- 4020 { "2.19": "519c8ac948f0b093eecaeee81b1ff92344210d31ce41a5b935d83a0084127c5a", "2.19-13": "174bf97a52e29ce61f3d2db725787e43a2cc7be9c2b07e4e1eb80d6ca3353c36", "2.19-15": "519c8ac948f0b093eecaeee81b1ff92344210d31ce41a5b935d83a0084127c5a", "2.7": "a883f5d8330e5a7e049cb3ead70e12e567a4be50c263518f9f1476fbb98219f5", "2.7-7": "a883f5d8330e5a7e049cb3ead70e12e567a4be50c263518f9f1476fbb98219f5", "latest": "519c8ac948f0b093eecaeee81b1ff92344210d31ce41a5b935d83a0084127c5a", "v3.1": "519c8ac948f0b093eecaeee81b1ff92344210d31ce41a5b935d83a0084127c5a", "v3.2": "519c8ac948f0b093eecaeee81b1ff92344210d31ce41a5b935d83a0084127c5a", "v3.3": "519c8ac948f0b093eecaeee81b1ff92344210d31ce41a5b935d83a0084127c5a", "v3.4": "519c8ac948f0b093eecaeee81b1ff92344210d31ce41a5b935d83a0084127c5a" }
This will be fixed with the following images: openshift3/jenkins-1-rhel7:1.651.2-54 openshift3/jenkins-2-rhel7:2.32-4 openshift3/jenkins-slave-base-rhel7:1.0-14 openshift3/jenkins-slave-maven-rhel7:3.3-15 openshift3/jenkins-slave-nodejs-rhel7:4-14
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1094