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 storage commands should mention the need of odo push for changes to take effect #2195

Closed
dharmit opened this issue Sep 27, 2019 · 0 comments · Fixed by #2198
Closed

odo storage commands should mention the need of odo push for changes to take effect #2195

dharmit opened this issue Sep 27, 2019 · 0 comments · Fixed by #2198

Comments

@dharmit
Copy link
Member

dharmit commented Sep 27, 2019

[kind/bug]

What versions of software are you using?

  • Operating System: all
  • Output of odo version: master

How did you run odo exactly?

  1. Created storage using odo storage create
  2. Deleted storage using odo storage delete

Actual behavior

  1. In case of odo storage create, the storage doesn't show up on remote pod.
  2. In case of odo storage delete, the storage doesn't get deleted from remote pod.

Expected behavior

odo storage create and odo storage delete commands should inform the user about the need of odo push for the changes to take effect on remote pod.

Any logs, error output, etc?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant