redhat-developer / redhat-developer/vscode-openshift-tools

Improve status of OpenShift connection (in OpenShift Application Explorer)

Open
#2,583 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

odov3-test priority/critical
Dominant language
TypeScript
Stars
123
Forks
63
Avg merge
6h 16m
Merged PRs (30d)
74

Description

Env: Linux, Fedora 36, CRC 2.9.0

I was logged to the CRC OCP in OS app. explorer, having a connection /api-crc-testing:6443/developer.
An Item was present (a component) under the connection (not sure about proper terminology).
I have manually stopped the crc from cli and call refresh on OpenShift Connection, then the component disappeared (which is alright).
But I still could call action on OS connection as it would have been connected (ie. create new project) which ended up with an error:

Failed to create Project with error 'Error: Command failed: "/home/odockal/.vscode/extensions/redhat.vscode-openshift-connector-0.7.0/out/tools/linux/odo" create namespace myproject2 -w ✗ unable to detect project support: Get "https://api.crc.testing:6443/apis/project.openshift.io/v1?timeout=32s": dial tcp 192.168.130.11:6443: connect: no route to host '

It should show the status of the connection (connected/disconnected) and it should not offer context menu item that are only for connected clusters.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the OpenShift Application Explorer: connect to CRC, stop CRC from the CLI, and refresh the OpenShift connection. Trace the connection refresh and context-menu handling; done means the connection visibly reports connected or disconnected and connected-only actions are unavailable when disconnected.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, typescript, vscode
Domain
cloud, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.