Bug 1710079
| Summary: | Missing button to create Cluster Logging CR after initial install of Cluster Logging operator | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Samuel Padgett <spadgett> |
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | amerdler, aos-bugs, jokerman, mifiedle, mmccomas, spadgett, yanpzhan, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Preivously in some cases you would see a whitescreen with no error in the web console if trying to create an operator resource immediately after installing an operator through Operator Hub. We now show a clear message in the console if trying to create a resource before it is available.
|
Story Points: | --- |
| Clone Of: | 1709964 | Environment: | |
| Last Closed: | 2019-10-16 06:28:42 UTC | Type: | --- |
| 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: | 1709964 | ||
| Bug Blocks: | |||
|
Comment 1
Samuel Padgett
2019-05-28 13:18:12 UTC
build: 4.2.0-0.nightly-2019-06-24-160709 console commit: 54fb3ee81a277b313798da833560acd6cb280790 Checked on ocp 4.2 env with above version. After install cluster logging operator, under "Installed Operator", find "Cluster Logging", click into it. Under "Cluster Logging" tab, there is info to indicate the resource status: The server doesn't have a resource type ClusterLogging. Try refreshing the page if it was recently added. After a while, ClusterLogging is added, and there is "Create Cluster Logging" button under "Cluster Logging" tab. The bug has been fixed, so move it to Verified. 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:2922 |