-
Notifications
You must be signed in to change notification settings - Fork 216
Adding Uninstall script for issue 168 #179
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
Conversation
Hi @tosin2013. Thanks for your PR. I'm waiting for a redhat-et member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rootfs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @oglok |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @tosin2013 for pushing this PR. We really appreciate your contributions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the microshift binary also be removed from the system? Cleaning up firewall rules, selinux config, stopping crio and uninstalling packages (if the desire is to have this script clean up everything from the install script) may be needed as well.
additional cleanup items based on feedback
i believe these are solved with the latest push
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cooktheryan @tosin2013 With @sallyom adding RPM building for microshift, would we use a hacky script like this? or is RPM uninstall going to call this one?
@guymguym I would say with RPM we would have a more formal removal process. This is in my opinion a nice supplement to help when running the install.sh or doing local development to set you back at a close to beginning state |
V ${SUDO} rm -rf /var/lib/rook | ||
V ${SUDO} rm -rf /var/lib/etcd | ||
V ${SUDO} rm -rf /var/lib/kubelet | ||
|
||
V ${SUDO} mkdir -p /var/lib/kubelet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rootfs WDYT Does it make sense to delete all these dirs here? Can there be any harm to a user that does not know that we do this cleanup? I think these are all "data" dirs, and the reason you used those originally was to make sure we remember to reset the state of rook/etcd/kubelet between install test cycles...
👍 Sounds good @cooktheryan ! |
❌ Deploy Preview for microshift failed. 🔨 Explore the source changes: e5b7fe7 🔍 Inspect the deploy log: https://app.netlify.com/sites/microshift/deploys/6179963af443970007acad41 |
closed will merge items in at #405 |
Adding clean up script for issue 168
#168