`odo preference view -o json` takes a long time if cluster is inaccessible

[datho7561]

/kind bug

What versions of software are you using?

Operating System: Fedora 39

Output of odo version:

===============================================
⚠  unable to fetch the cluster server version
===============================================
odo v3.15.0 (10b5e8a8f)

Podman Client: 4.9.0

How did you run odo exactly?

Set my ~/.kube/config to point to my crc cluster, which is stopped. Then I run : odo preference view -o json

Actual behavior

Takes around 40 seconds

Expected behavior

Takes < 1 second

Any logs, error output, etc?

[datho7561]

It seems like it's checking the status of the cluster, but I don't see why this would be needed for this command.

[rm3l]

odo preference view lists all the Devfile Registries odo can use, and (since odo v3.8.0) it also tries to list those coming from the current cluster. That's why it is trying to contact the current cluster.
More details in https://odo.dev/docs/user-guides/advanced/using-in-cluster-devfile-registry/

Actual behavior

Takes around 40 seconds

I guess any oc/kubectl command communicating with the cluster would take the same amount of time, right?

[datho7561]

Okay, thanks! I didn't know that the cluster could provide Devfiles

I guess any oc/kubectl command communicating with the cluster would take the same amount of time, right?

Yes, odo version takes around the same amount of time as odo preference view.

[github-actions]

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

[rm3l]

/remove-lifecycle stale
/lifecycle frozen