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

"odo catalog list components --all" displays components without displaying name #3340

Closed
groeges opened this issue Jun 12, 2020 · 4 comments
Closed
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.

Comments

@groeges
Copy link
Contributor

groeges commented Jun 12, 2020

/kind bug

What versions of software are you using?

Operating System:
Mac OS

Output of odo version:
odo version
odo v1.2.2 (dfaa739)

Server: https://9.30.194.54:6443
Kubernetes: v1.16.2

How did you run odo exactly?

odo catalog list components --all

Actual behavior

Add the devfilev2 registry:
odo registry add devfilev2 https://raw.githubusercontent.com/odo-devfiles/registry/master

odo registry list

NAME          URL
che           https://che-devfile-registry.openshift.io
steve         https://raw.githubusercontent.com/groeges/devfile-registry/master
devfilev2     https://raw.githubusercontent.com/odo-devfiles/registry/master

odo catalog list components --all

odo catalog list components --all
Odo OpenShift Components:
NAME              PROJECT       TAGS                        SUPPORTED
java              openshift     11,8,latest                 YES
nodejs            openshift     10-SCL,8,8-RHOAR,latest     YES
dotnet            openshift     2.1,2.2,3.0,latest          NO
golang            openshift     1.11.5,latest               NO
httpd             openshift     2.4,latest                  NO
modern-webapp     openshift     10.x,latest                 NO
nginx             openshift     1.10,1.12,latest            NO
perl              openshift     5.24,5.26,latest            NO
php               openshift     7.0,7.1,7.2,latest          NO
python            openshift     2.7,3.6,latest              NO
ruby              openshift     2.4,2.5,latest              NO

Odo Devfile Components:
NAME                        DESCRIPTION                                   REGISTRY      SUPPORTED
openLiberty                 Open Liberty microservice in Java             steve         YES
maven                       Upstream Maven and OpenJDK 11                 steve         YES
java-spring-boot            Spring Boot® using Java                       steve         YES
                            Upstream Quarkus with Java+GraalVM            devfilev2     NO
                            Open Liberty microservice in Java             devfilev2     NO
                            Upstream Maven and OpenJDK 11                 devfilev2     NO
                            Stack with NodeJS                             steve         NO
                            Stack with NodeJS 10                          devfilev2     NO
                            Spring Boot® using Java                       devfilev2     NO
java-maven                  Java Stack with OpenJDK 11 and Maven 3.6.0    che           NO

notice the entries for registry devfilev2 are unsupported and do not display the name.

Expected behavior

As odo is now supposed to support devfilev2 I would have expected the devfilev2 components to be marked SUPPORTED=YES and more importantly the name should be displayed.

Odo Devfile Components:
NAME                        DESCRIPTION                                   REGISTRY      SUPPORTED
openLiberty                 Open Liberty microservice in Java             steve         YES
maven                       Upstream Maven and OpenJDK 11                 steve         YES
java-spring-boot            Spring Boot® using Java                       steve         YES
quarkus                     Upstream Quarkus with Java+GraalVM            devfilev2     YES
openLiberty                 Open Liberty microservice in Java             devfilev2     YES
maven                       Upstream Maven and OpenJDK 11                 devfilev2     YES
nodejs                      Stack with NodeJS                             steve         YES
nodejs                      Stack with NodeJS 10                          devfilev2     YES
java-spring-boot            Spring Boot® using Java                       devfilev2     YES
java-maven                  Java Stack with OpenJDK 11 and Maven 3.6.0    che           NO

Any logs, error output, etc?

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 12, 2020
@GeekArthur
Copy link
Contributor

GeekArthur commented Jun 12, 2020

It's a known issue and currently odo catalog doesn't support devfile 2.0. This issue should be handled with #3249 and #2938 together, @maysunfaisal will implement those features/support. Also new format design including SUPPORTED column design will deliver with the changes.

@maysunfaisal
Copy link
Contributor

yes, watch out for PR #3291

@amitkrout amitkrout added the area/devfile-spec Issues or PRs related to the Devfile specification and how odo handles and interprets it. label Jun 13, 2020
@elsony
Copy link

elsony commented Aug 4, 2020

@groeges devfile 2.0 support is currently in the driver. Can you retry to see if you can still reproduce the problem?

@girishramnani
Copy link
Contributor

so I tried this command and we dont have --all anymore for odo catalog list components
and the output now has the component names. Hence closing

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
None yet
Development

No branches or pull requests

7 participants