This repository was archived by the owner on Apr 1, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 1, 2026. It is now read-only.
odo preference view -o json takes a long time if cluster is inaccessible #7205
Description
/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
Activity
datho7561 commentedon Feb 5, 2024
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 commentedon Feb 5, 2024
odo preference viewlists all the Devfile Registriesodocan use, and (sinceodo 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/
I guess any
oc/kubectlcommand communicating with the cluster would take the same amount of time, right?datho7561 commentedon Feb 5, 2024
Okay, thanks! I didn't know that the cluster could provide Devfiles
Yes,
odo versiontakes around the same amount of time asodo preference view.github-actions commentedon May 6, 2024
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 commentedon May 6, 2024
/remove-lifecycle stale
/lifecycle frozen