Bug 1829118
| Summary: | RFE: Request a more detailed output of the upgrade process | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Nick Poyant - npoyant <npoyant> |
| Component: | Cluster Version Operator | Assignee: | Lalatendu Mohanty <lmohanty> |
| Status: | CLOSED DUPLICATE | QA Contact: | liujia <jiajliu> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.z | CC: | aos-bugs, jokerman, wking |
| Target Milestone: | --- | ||
| Target Release: | 4.5.0 | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-19 03:26:47 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
Nick Poyant - npoyant@redhat.com
2020-04-28 22:30:28 UTC
setting target release to take this off our 4.4.0 blocker list, but this bug should be closed and replaced w/ a JIRA ticket on our RFE project. Have you tried "$ oc get clusterversion -o yaml or -o json"? I am familiar with the output. Is it possible to show something like that in the UI? I am familiar with the output. Is it possible to show something like that in the UI or some type of live stream output of a log file? > Is it possible to show something like that in the UI or some type of live stream output of a log file? Especially during update, the CVO bumps some 400 odd manifests, so I'm not in favor of pushing updates to ClusterVersion on every sync(-attempt). On the other hand, I'm fine mentioning every so often which manifest(s) we happen to be working on, and definitely any that have recently failed. That's one of the possible solutions for bug 1768255 too, so closing this one as a dup. *** This bug has been marked as a duplicate of bug 1768255 *** |