-
Notifications
You must be signed in to change notification settings - Fork 244
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 delete
is not deleting user created storage
#2710
Comments
From the Integration tests[1] it is evident that we want to delete user pvc with The above tests is also missed to catch that pvc is not deleted |
as discussed with @kadel we need to delete user created pvc with |
You can add owner reference to the pvc and that should get deleted if dc is deleted |
It's already there in PVC since we merged #2125. Unless there's a bug in the code added via that PR. 😉 |
No ownerReference being passed here :) |
Umm, are you looking at the right place? I see two calls to |
While |
I recently raised a PR which was supposed to update owner references for storage #2533. The problem is in the function /assign |
@mik-dass Thanks!! |
/kind bug
What versions of software are you using?
Operating System:
Output of
odo version
:How did you run odo exactly?
odo component has following storage.
When
odo delete
command is run, it gives message of deleting storage but it is not actually deleting it.Actual behavior
What should be the behavior of odo when
odo delete
command is run. It should delete user created pvc along with or not?I think Ideally user created persistent volume to have persisted data. so deleting along with component deletion is not right.
option1: Delete user created storage with
odo delete
option2: Do not Delete user created storage with
odo delete
odo delete
needs to be updated.odo push
afterodo delete
? as it will give errorstorage already exist
. Proceed for component creation and show storage exist error as message?Expected behavior
Any logs, error output, etc?
The text was updated successfully, but these errors were encountered: