Bug 1328392
| Summary: | Unclear process for getting image updates. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Miheer Salunke <misalunk> |
| Component: | Cluster Version Operator | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED ERRATA | QA Contact: | liujia <jiajliu> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.1.0 | CC: | aos-bugs, bleanhar, dherrman, erich, jokerman, mamburn, misalunk, mmccomas, sgraf, smunilla, sreber, tbielawa |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:40:18 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
Miheer Salunke
2016-04-19 09:53:18 UTC
Talking with Stanislav a little bit ago I think the best solution we have today is for customer to subscribe to errata notifications for their products: https://access.redhat.com/solutions/135503 We've had a good meeting last Wednesday. I've shared the mid- and long-term vision around many items mentioned in this BZ. It seems that we will address most of them over time but not immediately. We've scheduled a follow-up mid of September to review if we will cover all aspects or not. Change status back to MODIFIED since we did not hit 4.0 Beta 2 now. btw, how should QE verify this bug in v4.0? Does we should verify an cluster upgrade functionally or verify it through document process? I believe 4.0 beta 2 will be upgradeable to beta 3. I'm certain we'll give QE docs on how to do that when the time comes if it's not obvious from the UI. In the worst case it will involve editing the clusterversion custom resource to trigger the process. Once we GA the admin console should have a button to upgrade everything. :) Install a beta3 cluster. # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.9 True False 15m Cluster version is 4.0.0-0.9 Access the OpenShift web-console. In [Administration]-[clustersettins] page, there are "update now" button for users to check available update list, and do upgrade directly. Choose "4.0.0-0.11" (Beta 3 patch 2) in above list, and do upgrade. Then you can monitor the "update status" in the same page. Some info as fllowing shown: Cluster update in progress. Working towards 4.0.0-0.11: downloading update. View Cluster Operators for more details. Cluster update in progress. Working towards 4.0.0-0.11: 11% complete. View Cluster Operators for more details. ... Upgrade succeed. # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.11 True False 2m22s Cluster version is 4.0.0-0.11 According to comment 18&comment22, in 4.x, now there is clear information about available update list and the cluster update status from UI. So verify the bug. 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-2019:0758 |