Bug 1912536 - Console Plugin CR for console-demo-plugin has wrong apiVersion
Summary: Console Plugin CR for console-demo-plugin has wrong apiVersion
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.7.0
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-04 16:58 UTC by Jakub Hadvig
Modified: 2021-02-24 15:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Wrong apiVersion for console-demo-plugin in the console repository Consequence: console-demo-plugin CR can't be created Fix: set proper v1alpha1 version on the console-demo-plugin CR Result: console-demo-plugin CR can be created
Clone Of:
Environment:
Last Closed: 2021-02-24 15:49:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 7700 0 None closed Bug 1912536: Put correct version on the console-demo-plugin CR 2021-02-04 03:42:16 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:50:01 UTC

Description Jakub Hadvig 2021-01-04 16:58:46 UTC
Description of problem:
Console Plugin CR for console-demo-plugin has wrong apiVersion

Version-Release number of selected component (if applicable):
4.7

How reproducible:
always

Steps to Reproduce:
1. Create ConsolePlugin CRD on the cluster from https://gist.github.com/jhadvig/8c10ca0fbf32703dc8c97af8f57f2228
2. Clone OpenShift 'Console' repository 
3. Try to create oc-manifest.yaml in the `frontend/dynamic-demo-plugin/oc-manifest.yaml`

Actual results:
console-demo-plugin CR wont be created since its in the wrong version - v1

Expected results:
console-demo-plugin CR will be created with right version - v1alpha1

Additional info:
ConsolePlugin CRD itself is part of https://github.com/openshift/api/pull/764 PR, thats why its not available on the cluster yet.

Comment 2 Yadan Pei 2021-01-12 05:57:11 UTC
1. Create ConsolePlugin CRD on the cluster from https://gist.github.com/jhadvig/8c10ca0fbf32703dc8c97af8f57f2228

2. Clone OpenShift 'Console' repository 

3. Try to create oc-manifest.yaml in the `frontend/dynamic-demo-plugin/oc-manifest.yaml`
# oc create -f frontend/dynamic-demo-plugin/oc-manifest.yaml
namespace/console-demo-plugin created
deployment.apps/console-demo-plugin created
service/console-demo-plugin created
consoleplugin.console.openshift.io/console-demo-plugin created

# oc get consoleplugin.console.openshift.io console-demo-plugin -o yaml
apiVersion: console.openshift.io/v1alpha1
kind: ConsolePlugin
metadata:
  creationTimestamp: "2021-01-12T05:55:15Z"
  generation: 1
  managedFields:
  - apiVersion: console.openshift.io/v1alpha1
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        .: {}
        f:displayName: {}
        f:service:
          .: {}
          f:basePath: {}
          f:name: {}
          f:namespace: {}
          f:port: {}
    manager: kubectl-create
    operation: Update
    time: "2021-01-12T05:55:15Z"
  name: console-demo-plugin
  resourceVersion: "686604"
  selfLink: /apis/console.openshift.io/v1alpha1/consoleplugins/console-demo-plugin
  uid: 8e75a1fb-4581-44ee-bc8d-2f062df7fb84
spec:
  displayName: OpenShift Console Demo Plugin
  service:
    basePath: /
    name: console-demo-plugin
    namespace: console-demo-plugin
    port: 9001

This is verified on 4.7.0-0.nightly-2021-01-10-070949

Comment 5 errata-xmlrpc 2021-02-24 15:49:41 UTC
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633


Note You need to log in before you can comment on or make changes to this bug.