Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-1624

The "OpenshiftConnector" plugin can't find proper image during component creation

XMLWordPrintable

    • False
    • False
    • +
    • Undefined
    • Hide

      Environment:

      • OCP 4.6 cluster
      • CRW 2.7 installed by operatorhub
      • TLS, oAuth enabled
      • Server image
        "registry.redhat.io/codeready-workspaces/server-rhel8@sha256:4b9b6416c1531e6d17cb83ab45a018b77ad5a6a2977f4c5f10deb4e3b0280960"
      • Devfile registry image
        "registry.redhat.io/codeready-workspaces/devfileregistry-rhel8@sha256:bf076a9417f3169819c53137e75c7844454d4deffc4da4a78bd0c65198aa6192"
      • Plugin registry image
        "registry.redhat.io/codeready-workspaces/pluginregistry-rhel8@sha256:9c36b109b000cccf086ac665591380ab84e9cbb37e61a99ae1ca7c5dd75e2a46"

      Steps to reproduce:

      • Go to dashboard and create workspace using devfile:
        apiVersion: 1.0.0
        metadata:
          name: test-workspace
        projects:
          - name: node-js
            source:
              location: 'https://github.com/maxura/nodejs-hello-world.git'
              type: git
              branch: master
        components:
          - id: redhat/vscode-openshift-connector/latest
            type: chePlugin
        
      • Go inside created workspace
      • Open the "OpenshiftConnector" view (left toolbar)
      • Login to the cluster (click to the cluster item in the plugin view and provide credentials)
      • Press the "F1" button and in the appeared drop down type and apply "OpenShift: New Component from local folder"
      • Select target project
      • Provide name for new project and component
      • In the appeared drop down select the "nodejs" image (also reproduces for the "java" image)
      • Select "10" version (also reproduces for 10-ubi8)
      • Pay attention that nothing happens
      • Open browser terminal and pay attention to the error

      Expected behavior:
      New component will be created and shown in the plugin view list

      Observed behavior:
      Unable to find selected image

      Show
      Environment: OCP 4.6 cluster CRW 2.7 installed by operatorhub TLS, oAuth enabled Server image "registry.redhat.io/codeready-workspaces/server-rhel8@sha256:4b9b6416c1531e6d17cb83ab45a018b77ad5a6a2977f4c5f10deb4e3b0280960" Devfile registry image "registry.redhat.io/codeready-workspaces/devfileregistry-rhel8@sha256:bf076a9417f3169819c53137e75c7844454d4deffc4da4a78bd0c65198aa6192" Plugin registry image "registry.redhat.io/codeready-workspaces/pluginregistry-rhel8@sha256:9c36b109b000cccf086ac665591380ab84e9cbb37e61a99ae1ca7c5dd75e2a46" Steps to reproduce: Go to dashboard and create workspace using devfile: apiVersion: 1.0.0 metadata: name: test-workspace projects: - name: node-js source: location: 'https: //github.com/maxura/nodejs-hello-world.git' type: git branch: master components: - id: redhat/vscode-openshift-connector/latest type: chePlugin Go inside created workspace Open the "OpenshiftConnector" view (left toolbar) Login to the cluster (click to the cluster item in the plugin view and provide credentials) Press the "F1" button and in the appeared drop down type and apply "OpenShift: New Component from local folder" Select target project Provide name for new project and component In the appeared drop down select the "nodejs" image (also reproduces for the "java" image) Select "10" version (also reproduces for 10-ubi8) Pay attention that nothing happens Open browser terminal and pay attention to the error Expected behavior: New component will be created and shown in the plugin view list Observed behavior: Unable to find selected image

      The "OpenshiftConnector" plugin can't find proper image during component creation

              ericwill@redhat.com Eric Williams
              iokhrime Ihor Okhrimenko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: