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

Invalid description when running 'odo dev --debug' #7197

Closed
sbouchet opened this issue Feb 2, 2024 · 2 comments
Closed

Invalid description when running 'odo dev --debug' #7197

sbouchet opened this issue Feb 2, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@sbouchet
Copy link

sbouchet commented Feb 2, 2024

/kind bug

What versions of software are you using?

Operating System: Fedora 39

Output of odo version: 3.15.0

How did you run odo exactly?

odo dev --platform podman --debug --forward-localhost
then
odo describe component

Actual behavior

output of the describe command:

Running in: Dev

Running on:
 •  podman: Dev

Dev Control Plane:
 •  podman
      API: http://localhost:20000/api/v1/
      Web UI: http://localhost:20000/

Forwarded ports:
 •  [podman] 127.0.0.1:20001 -> runtime:3000
    Name: http-node
 •  [podman] 127.0.0.1:20002 -> runtime:5858
    Name: debug
    Exposure: none
    Debug: true

Supported odo features:
 •  Dev: true
 •  Deploy: false
 •  Debug: true

Expected behavior

as Debug is supported, i'm running using the --debug and thus it must be returned when describing the component.
it's actually the same output for the dev only command.the only change is the debug port.

Any logs, error output, etc?

Capture d’écran du 2024-02-02 14-53-36

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 2, 2024
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Feb 2, 2024
Copy link
Contributor

github-actions bot commented May 3, 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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 3, 2024
Copy link
Contributor

github-actions bot commented Jun 2, 2024

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 2, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 2, 2024
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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
Archived in project
Development

No branches or pull requests

1 participant