Bug 1420229
Summary: | [IntService_public_295] upgrade from 3.4 metrics failed, no object is refreshed | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Peng Li <penli> |
Component: | Installer | Assignee: | Jeff Cantrill <jcantril> |
Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.5.0 | CC: | aos-bugs, bbarcaro, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | 3.5.z | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-14 21:01:20 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1306678 |
Description
Peng Li
2017-02-08 09:11:59 UTC
check the pod name, no pod is deleted and created with newer version. Reran this scenario, what I find is: RC has image like: registry.ops.openshift.com/openshift3/metrics-cassandra:3.5.0 Pod has image: registry.ops.openshift.com/openshift3/metrics-cassandra:3.4.1 It appears the issue is the pods need to be bounced to pick up the new image since they do not automatically redeploy. Looking into what can be done to cycle the RC. Lowering severity as its not a blocker. Commit pushed to master at https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible/commit/ac23d6fc37dd98be8ad4ecc5a924d482e6e74957 bug 1420229. Bounce metrics components to recognize changes on updates or upgrades @jcantril, this pr is merged. https://github.com/openshift/openshift-ansible/pull/3309 And 3.4.1 to 3.5.0 upgrade test scenario is passed, please feel free to set it to ON_QA, then I can close it. set status to verified based on comment #6. 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:3438 |