Bug 1780835
Summary: | Serverless Service / route models clash with other models | ||
---|---|---|---|
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.3.0 | CC: | aos-bugs, jokerman, yapei |
Target Milestone: | --- | ||
Target Release: | 4.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1780392 | Environment: |
Version: 4.3.0-0.nightly-2019-12-04-054458
Cluster ID: cf4140ef-20ce-4aea-a4cc-9d3410c49891
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:71.0) Gecko/20100101 Firefox/71.0
|
Last Closed: | 2020-01-23 11:18:15 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: | 1780392 | ||
Bug Blocks: |
Description
Samuel Padgett
2019-12-07 13:52:24 UTC
1. cluster admin subscribed the 'OpenShift Serverless Operator' and make sure it's installed successfully 2. Serverless -> Services -> click 'Create Service' button -> Create, it shows Tech Preview on YAML editor page 3. Also on Serverless -> Routes, Revisions page, it also shows 'Tech Preview' and resource icon color for services, routes, revisions is yellow not green(Networking services, routes...) Also the HTTP requests are sending to correct API /api/kubernetes/apis/serving.knative.dev/v1beta1/namespaces/openshift-operators/services?watch=true&resourceVersion=122631 /api/kubernetes/apis/serving.knative.dev/v1beta1/namespaces/openshift-operators/services Verified on 4.3.0-0.nightly-2019-12-08-215349 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-2020:0062 |