| Summary: | OpenShift metrics does not work after upgrade from OpenShift 3.2 to OpenShift 3.3 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Elvir Kuric <ekuric> |
| Component: | Hawkular | Assignee: | Matt Wringe <mwringe> |
| Status: | CLOSED NOTABUG | QA Contact: | Peng Li <penli> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.1 | CC: | aos-bugs, ekuric, jeder, pmackinn |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | tstclair@redhat.com | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-27 16:14:04 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: | |
|
Description
Elvir Kuric
2016-09-02 08:32:51 UTC
Are you also updating Metrics to version 3.3? The console is using apis which are only available with the Metrics meant for 3.3, which could explain why the console is failing. When updating version of OpenShift you must also update the metrics components. Please see the docs: https://docs.openshift.com/enterprise/3.2/install_config/upgrading/automated_upgrades.html#automated-upgrading-cluster-metrics [those are the 3.2 docs, but its the same update procedure for 3.3] Seeing the same thing with a yum update to 3.3. Noticed that it grabbed the docker hub metrics/cassandra/heapster images for some reason. Is that correct? e2d419c54f56 openshift/origin-metrics-heapster:latest "heapster-wrapper.sh " 14 hours ago Up 14 hours k8s_heapster.4ce7cca2_heapster-xjpe1_openshift-infra_c8e6ba62-868e-11e6-8311-246e960f19fc_baa53e21 # docker images | grep heapster docker.io/openshift/origin-metrics-heapster latest d10568760a84 3 days ago 994.8 MB Sorry, guess I had grabbed the origin version of metrics-deployer.yaml. Corrected that and followed updated docs for 3.3 but same issue. oadm diagnostics MetricsApiProxy reports no warnings or errors. Looks like cluster roles needed to be fixed up this way post yum upgrade. # oadm policy reconcile-cluster-roles --confirm -o name clusterrole/sudoer clusterrole/cluster-reader clusterrole/system:build-strategy-jenkinspipeline clusterrole/admin clusterrole/edit clusterrole/view clusterrole/basic-user clusterrole/self-access-reviewer clusterrole/cluster-status clusterrole/system:image-builder clusterrole/system:image-pruner clusterrole/system:image-signer clusterrole/system:deployer clusterrole/system:router clusterrole/system:registry clusterrole/system:node clusterrole/system:sdn-reader clusterrole/system:discovery clusterrole/registry-admin clusterrole/registry-editor Closing this as not a bug as it appears the cluster role update step was skipped during the update. When running this command, things appear to function again. |