Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Devfile] odo catalog can't list components on non-OpenShift clusters #2706

Closed
johnmcollier opened this issue Mar 11, 2020 · 2 comments · Fixed by #2749
Closed

[Devfile] odo catalog can't list components on non-OpenShift clusters #2706

johnmcollier opened this issue Mar 11, 2020 · 2 comments · Fixed by #2749
Assignees
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/bug Categorizes issue or PR as related to a bug.
Projects

Comments

@johnmcollier
Copy link
Member

johnmcollier commented Mar 11, 2020

/kind bug

What versions of software are you using?

odo from master

Operating System:
macOS

How did you run odo exactly?

  1. Started Minikube
  2. Enabled experimental mode
  3. Ran odo catalog list components

odo reported the following error:

johns-mbp-3:odo johncollier$ ./odo catalog list components
 ✗  unable to list imagestreams: the server could not find the requested resource (get imagestreams.image.openshift.io).
unable to list imagestreams: the server could not find the requested resource (get imagestreams.image.openshift.io)

Now, this is happening since I'm not running on OpenShift and thus there are no imagestreams that can be retrieved. Since odo2 and its devfile support is Kube-generic, it should at least return the list of devfile components when running on a non-OpenShift cluster.

/kind bug
/area devfile

@openshift-ci-robot openshift-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. labels Mar 11, 2020
@johnmcollier
Copy link
Member Author

This one's a little tricky:

  • With experimental mode enabled, we can list both "odo classic" image stream components from OpenShift and devfile components,
  • But we can only use devfile components when doing an odo push with experimental mode enabled.

So I think we've got at least a couple options:

  1. Remove the error check from https://github.com/openshift/odo/blob/master/pkg/odo/cli/catalog/list/components.go#L45
    • A little risky if running on OpenShift and there's a legitimate issue getting the image streams
  2. Only retrieve the devfile components when experimental mode is enabled, knowing that odo push with experimental mode currently only supports devfile components

@elsony elsony added this to For consideration in Sprint 181 via automation Mar 12, 2020
@elsony elsony moved this from For consideration to To do in Sprint 181 Mar 12, 2020
@GeekArthur
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. kind/bug Categorizes issue or PR as related to a bug.
Projects
No open projects
Sprint 181
  
Done
3 participants