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

Add logic to the security wrappers activation script removing old wrapper paths if they exist #24164

Closed
ixmatus opened this issue Mar 21, 2017 · 1 comment

Comments

@ixmatus
Copy link
Contributor

ixmatus commented Mar 21, 2017

Issue description

This is specifically in reference to #23641 which addresses a regression I introduced in another PR adding setcap wrapper support with additional logic for cleaning up the legacy wrapper paths; at the time I hadn't thoroughly thought through nor tested the migration scenarios until a user experienced the problem themselves.

We went ahead and merged #23641 to unblock 17.03 and @abbradar had a good suggestion for discriminating on the active current system when checking for the legacy wrapper paths to be removed and removing them.

This ticket tracks the work we need to do after 17.03 is released to cleanup the legacy wrapper paths safely.

@mmahut
Copy link
Member

mmahut commented Aug 12, 2019

This has been merged in.

@mmahut mmahut closed this as completed Aug 12, 2019
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

No branches or pull requests

2 participants