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 describe component fails when trying to get info about "non-odo" component #6584

Closed
kadel opened this issue Feb 9, 2023 · 1 comment · Fixed by #6615
Closed

odo describe component fails when trying to get info about "non-odo" component #6584

kadel opened this issue Feb 9, 2023 · 1 comment · Fixed by #6615
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Milestone

Comments

@kadel
Copy link
Member

kadel commented Feb 9, 2023

/kind bug

What versions of software are you using?

Operating System:

Output of odo version:
odo v3.6.0 (a035764)

How did you run odo exactly?

  • created a new component using OpenShift Dev Console (+Add -> Samples -> Basic Node.js)
  • run odo list
    ▶ odo list
     ✓  Listing resources from the namespace "tkral-dev" [9s]
    
    Components:
     NAME                       PROJECT TYPE  RUNNING IN  MANAGED
     * java-springboot-starter  springboot    None        Unknown
     nodejs-basic               Unknown       None        Unknown
     devfile-sample-git         Unknown       None        Unknown
     modelmesh-controller       Unknown       None        modelmesh-controller
    
  • run odo describe component
    ▶ odo describe component --name nodejs-basic
     ✗  no component found with name "nodejs-basic" in the namespace "tkral-dev"
    

Actual behavior

odo describe component complains that the component nodejs-basic doesn't exists, but odo list sees it. This is confusing behaviour. One odo commands sees that compoent, but other doesn't

Expected behavior

It need to be possible to run describe command on every item listed in the list output.

Any logs, error output, etc?

Odo won't be albe to get all the information from the compoentn that is not managed by odo. This is ok. THe output can be limited to only information that odo can obtain.

/kind bug
/priority high

@openshift-ci openshift-ci bot added kind/bug Categorizes issue or PR as related to a bug. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). labels Feb 9, 2023
@rm3l rm3l added this to odo Project Feb 9, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Feb 9, 2023
@feloy
Copy link
Contributor

feloy commented Feb 15, 2023

Floows the case "Describe"
Rely on best-practices labels to determine information

Ingresses / Routes should be displayed it such resources exist with best-practices labels

@feloy feloy self-assigned this Feb 15, 2023
@feloy feloy moved this to In Progress 🚧 in odo Project Feb 22, 2023
@feloy feloy mentioned this issue Feb 22, 2023
3 tasks
@feloy feloy moved this from In Progress 🚧 to In Review 👀 in odo Project Feb 22, 2023
@github-project-automation github-project-automation bot moved this from In Review 👀 to Done ✅ in odo Project Feb 27, 2023
@rm3l rm3l added this to the v3.8.0 🚀 milestone Feb 27, 2023
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants