Loading...

XML

Word

Printable

Blocked:
False
Ready:
False
Release Note Text:

Hide
= Failing to activate the `Tooling for Apache Camel K by Red Hat` extension

Currently, activation of the `Tooling for Apache Camel K by Red Hat` extension fails with the following error message: *Activating extension 'Tooling for Apache Camel K by Red Hat' failed: Dependent extension 'redhat.vscode-commons' is not installed.* There is currently no workaround for this issue.

Show
= Failing to activate the `Tooling for Apache Camel K by Red Hat` extension Currently, activation of the `Tooling for Apache Camel K by Red Hat` extension fails with the following error message: *Activating extension 'Tooling for Apache Camel K by Red Hat' failed: Dependent extension 'redhat.vscode-commons' is not installed.* There is currently no workaround for this issue.
Market:

Environment:

Server image: "quay.io/crw/server-rhel8@sha256:7d1dbcb9c2d39c25f563f5533070c882aaa673fc8a769ba4fae4e4bca2523db7"

Devfile registry image: "quay.io/crw/devfileregistry-rhel8@sha256:056f3fbb1eb73cc6a2e4333d0d9b1d00dedec31630c59c747aeaaced569eb459"

Plugin registry image: "registry.redhat.io/codeready-workspaces/pluginregistry-rhel8@sha256:8a8efbdf41d229cc0071239764af363edf259cfdcc711dd47b5f880d47e9f71e"

Steps to reproduce:

Go to dashboard and create workspace using the "Tooling for Apache Camel K" default devfile
Go inside created workspace and open the "camel-k-examples/languages/hello.xml" file
Pay attention to the error notification

Expected behavior:
The VS Code Tooling for Apache Camel K is activated.

Observed behavior:
The error notification shown

is blocked by

CRW-2022 ppc-006 failing to run rhpkg commands (missing kerb session?)

is related to

CRW-2212 stop building and including kamel binary in plugin-kubernetes container