Red Hat Bugzilla – Bug 1476712
default logging/metrics image tag should be set to v3.6 but not 3.6.0
Last modified: 2017-08-16 15:51 EDT
All of the images do have the 3.6.0 tag on them now, maybe they didn't before? and Sam has confirmed that this will be the case when they go live so I think this is how it should be.
Can you verify the reason for the curator pod crashlooping?
(In reply to Scott Dodson from comment #1)
> All of the images do have the 3.6.0 tag on them now, maybe they didn't
> before? and Sam has confirmed that this will be the case when they go live
> so I think this is how it should be.
> Can you verify the reason for the curator pod crashlooping?
Unfortunately, the env was terminated. After searching, found https://bugzilla.redhat.com/show_bug.cgi?id=1445568 should be the same case like here. Just because the 3.6.0 image on ops registry is out-of-date, not the latest one.
Here in this bug I am requesting installer change default image tag to v3.6, so that make sure always latest image is being pulled whatever using which registry.
Of course, if we could make sure the images which will go live are tagged with 3.6.0 and up-to-date, it is okay to fix this bug after 3.6 GA.
https://github.com/openshift/openshift-ansible/pull/4958 for master branch, testing real quick
https://github.com/openshift/openshift-ansible/pull/4966 for release-3.6 branch
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.