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.

Sign up for GitHub

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

Jump to bottom

state transfer sub command does not clean up the resources it creates #28

Open
alaypatel07 opened this issue Aug 24, 2021 · 4 comments
Open

state transfer sub command does not clean up the resources it creates #28

alaypatel07 opened this issue Aug 24, 2021 · 4 comments
Assignees
@pranavgaikwad
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@alaypatel07
Copy link
Contributor

In order to clean up manually before running use the following command:

$ oc --context=destination-ctx -n pvc-transfer-source delete pod,cm,secret,svc,route -l app=crane2 && oc --context=destination-ctx -n pvc-transfer-source delete pvc foo && oc --context=source-ctx -n pvc-transfer-source delete pod,cm,secret,svc,route -l app=crane2

follow up from #19
@djzager djzager added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jun 18, 2022
@eriknelson
Copy link
Contributor

/kind bug
/priority critical

@openshift-ci openshift-ci bot added kind/bug Categorizes issue or PR as related to a bug. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 24, 2022
@eriknelson eriknelson removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jun 24, 2022
@eriknelson
Copy link
Contributor

/triage accepted

@openshift-ci openshift-ci bot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Jun 24, 2022
@github-actions
Copy link

This issue synced with: https://issues.redhat.com/browse/MTRHO-63

1 similar comment
@github-actions
Copy link

This issue synced with: https://issues.redhat.com/browse/MTRHO-63

@eriknelson eriknelson assigned djzager and pranavgaikwad and unassigned djzager Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pranavgaikwad pranavgaikwad

Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@eriknelson @djzager @alaypatel07 @pranavgaikwad