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 projects" doesn't exists as command #3379

Closed
rhuss opened this issue Jun 18, 2020 · 4 comments
Closed

"odo projects" doesn't exists as command #3379

rhuss opened this issue Jun 18, 2020 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@rhuss
Copy link
Contributor

rhuss commented Jun 18, 2020

/kind bug

What versions of software are you using?

Operating System: macOS

Output of odo version:

odo v1.2.2 (53530e0e5)

Server: https://api.rhuss-dev.devcluster.openshift.com:6443
Kubernetes: v1.17.1+f63db30

How did you run odo exactly?

odo login -u kubeadmin -p WWCNK-XmYus-3NDS3-8HhuJ
Connecting to the OpenShift cluster

Server [https://localhost:8443]: https://api.rhuss-dev.devcluster.openshift.com:6443
Login successful.

You have access to 60 projects, the list has been suppressed. You can list all projects with 
'odo projects'

Using project "default".

$ odo projects
.....
✗  Invalid command - see available commands/subcommands above

Also calling odo projects results in the usage message printed twice, once on standard out and once on standard error

Output of odo projects
odo is a CLI tool for running OpenShift applications in a fast and automated manner.
Reducing the complexity of deployment, odo adds iterative development without the worry of deploying your source code.

Find more information at https://github.com/openshift/odo

Usage:
  odo [flags]
  odo [command]

Examples:
  # Creating and deploying a Node.js project
  git clone https://github.com/openshift/nodejs-ex && cd nodejs-ex
  odo create nodejs
  odo push
  
  # Accessing your Node.js component
  odo url create

Commands:
  app         Perform application operations (delete, describe, list)
  catalog     Catalog related operations (describe, list, search)
  component   Manage components (create, delete, describe, link, list, log, push, unlink, update, watch)
  config      Change or view configuration (set, unset, view)
  debug       Debug commands (info, port-forward)
  preference  Modifies preference settings (set, unset, view)
  project     Perform project operations (create, delete, get, list, set)
  service     Perform service catalog operations (create, delete, list)
  storage     Perform storage operations (create, delete, list)
  url         Expose component to the outside world (create, delete, describe, list)

Utility Commands:
  help        Help about any command
  login       Login to cluster
  logout      Log out of the current OpenShift session
  utils       Utilities for terminal commands and modifying odo configurations (terminal)
  version     Print the client version information

Component Shortcuts:
  create      Create a new component 
  delete      Delete component 
  describe    Describe component 
  link        Link component to a service or component 
  list        List all components in the current application 
  log         Retrieve the log for the given component 
  push        Push source code to a component 
  unlink      Unlink component to a service or component 
  update      Update the source code path of a component 
  watch       Watch for changes, update component on change 

Flags:
      --add_dir_header           If true, adds the file directory to the header
      --complete                 Install completion for odo command
  -h, --help                     Help for odo
      --log_file string          If non-empty, use this log file
      --log_file_max_size uint   Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --skip_headers             If true, avoid header prefixes in the log messages
      --skip_log_headers         If true, avoid headers when opening log files
      --uncomplete               Uninstall completion for odo command
  -v, --v Level                  Number for the log level verbosity. Level varies from 0 to 9 (default 0).
      --vmodule moduleSpec       Comma-separated list of pattern=N settings for file-filtered logging
  -y, --y                        Don't prompt user for typing 'yes' when installing completion

Use "odo [command] --help" for more information about a command.
Error: Invalid command - see available commands/subcommands above
Usage:
  odo [flags]
  odo [command]

Examples:
  # Creating and deploying a Node.js project
  git clone https://github.com/openshift/nodejs-ex && cd nodejs-ex
  odo create nodejs
  odo push
  
  # Accessing your Node.js component
  odo url create

Commands:
  app         Perform application operations (delete, describe, list)
  catalog     Catalog related operations (describe, list, search)
  component   Manage components (create, delete, describe, link, list, log, push, unlink, update, watch)
  config      Change or view configuration (set, unset, view)
  debug       Debug commands (info, port-forward)
  preference  Modifies preference settings (set, unset, view)
  project     Perform project operations (create, delete, get, list, set)
  service     Perform service catalog operations (create, delete, list)
  storage     Perform storage operations (create, delete, list)
  url         Expose component to the outside world (create, delete, describe, list)

Utility Commands:
  help        Help about any command
  login       Login to cluster
  logout      Log out of the current OpenShift session
  utils       Utilities for terminal commands and modifying odo configurations (terminal)
  version     Print the client version information

Component Shortcuts:
  create      Create a new component 
  delete      Delete component 
  describe    Describe component 
  link        Link component to a service or component 
  list        List all components in the current application 
  log         Retrieve the log for the given component 
  push        Push source code to a component 
  unlink      Unlink component to a service or component 
  update      Update the source code path of a component 
  watch       Watch for changes, update component on change 

Flags:
      --add_dir_header           If true, adds the file directory to the header
      --complete                 Install completion for odo command
  -h, --help                     Help for odo
      --log_file string          If non-empty, use this log file
      --log_file_max_size uint   Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --skip_headers             If true, avoid header prefixes in the log messages
      --skip_log_headers         If true, avoid headers when opening log files
      --uncomplete               Uninstall completion for odo command
  -v, --v Level                  Number for the log level verbosity. Level varies from 0 to 9 (default 0).
      --vmodule moduleSpec       Comma-separated list of pattern=N settings for file-filtered logging
  -y, --y                        Don't prompt user for typing 'yes' when installing completion

Use "odo [command] --help" for more information about a command.

 ✗  Invalid command - see available commands/subcommands above

Expected behavior

The login command mentions odo projects for listing all projects, but that command does not exists. I would either expect that command to be available or the login message being adapted.

Calling an invalid command should print the error only once, too.

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

This has been fixed by this #3262 . @kadel @girishramnani good to close?

@girishramnani
Copy link
Contributor

sure. please dont forget to use the PR template to avoid such dangling issues. #3262 (comment)

@devang-gaur
Copy link
Contributor

actually I just saw this issue a while back. didn't know about this issue when I created the PR.

@mik-dass
Copy link
Contributor

actually I just saw this issue a while back. didn't know about this issue when I created the PR.

This issue was created after #3262 was merged.

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

No branches or pull requests

5 participants