Bug 1306665
Summary: | [metrics] update metrics-deployer template to use latest image versions | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Evgheni Dereveanchin <ederevea> |
Component: | Hawkular | Assignee: | Brenton Leanhardt <bleanhar> |
Status: | CLOSED ERRATA | QA Contact: | chunchen <chunchen> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.1.0 | CC: | aos-bugs, bleanhar, wsun, xiazhao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openshift-ansible-3.0.40-1.git.0.cfb19e2.el7aos | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-29 12:57:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Evgheni Dereveanchin
2016-02-11 14:37:19 UTC
Verified with openshift-ansible-3.0.40-1.git.22.da21865.el7aos.noarch, current results: name: IMAGE_VERSION value: "3.1.1" In order for the incoming releases in future, may it be possible to change IMAGE_VERSION to latest? Hi Zhao Xia, I'm a little confused when you say "Verified with openshift-ansible-3.0.40-1.git.22.da21865.el7aos.noarch". Do you mean to say there is still a problem? For now it wouldn't be safe to set the image version to 'latest'. That could result in someone installing a version of metrics-deployer that isn't compatible with their environment. We believe the 3.1.1 version is compatible with OSE 3.1.0 though. If you are seeing a bug please include more information. Hi Brenton, I meant the current bug fix (to set IMAGE_VERSION=3.1.1) may not work in future releases, say if we will release 3.2.0, 3.x.0... in future. And now I understand that it is unsafe to set image version to 'latest', so closing this issue as fixed, and I will track the potential problem by individual bugs in the releases post 3.1.1. Thanks, Xia That makes sense. We'll definitely want to track the real fix for this problem so feel free to create another bug for that. 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-2016:0311 |