Bug 1683777
| Summary: | Create button of the ClusterLogging is missing from UI | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> | ||||
| Component: | OLM | Assignee: | Evan Cordell <ecordell> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Salvatore Colangelo <scolange> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.1.0 | CC: | aos-bugs, jcantril, jiazha, rmeggins, sponnaga | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-06-04 10:44:42 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: | |||||||
| Attachments: |
|
||||||
|
Description
Jeff Cantrill
2019-02-27 18:56:09 UTC
Created attachment 1539250 [details]
screenshot
Thanks for your report! But, this issue belongs to the Operator itself or the UI, nothing with the OLM. Transfer it to Logging component. (In reply to Jian Zhang from comment #2) > Thanks for your report! But, this issue belongs to the Operator itself or > the UI, nothing with the OLM. Is OLM not the component which provides the UI. The cluster logging operator has no control or means to affect the UI unless there is some hint in the CSV that is missing. Moving back to OLM per the original advisement by Jessica Jeff,
> Actual results: No button. See screen shot
I think the "button" belongs to the static component of UI. What do you think?
https://github.com/openshift/console/pull/1343 Should be fixed here The Button now is present 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 |