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

Inform users of potential manual cleanup of user-data.isos in longstanding Rancher envs. #1535

Open
jakefhyde opened this issue Oct 30, 2024 · 1 comment · May be fixed by #1601
Open

Inform users of potential manual cleanup of user-data.isos in longstanding Rancher envs. #1535

jakefhyde opened this issue Oct 30, 2024 · 1 comment · May be fixed by #1601
Assignees
Milestone

Comments

@jakefhyde
Copy link
Contributor

Related Issues

SURE-6985
rancher/rancher#25073

Summary

Some point before v2.9.2 was released, rancher/rancher#25073 no longer was reproducible. Although the issue no longer occurs, vSphere environments used by Rancher prior to v2.9.2 may still see an abundance of user-data.iso files related to infrastructure that no longer exists, which requires manual cleanup.

NOTE: While it was suggested to use a script to perform the cleanup, I personally don't think this will be doable, as a single vSphere instance can be used across multiple Rancher instances as well as standalone, so there is not a good mechanism for determining which folders/files are not in use.

@jakefhyde
Copy link
Contributor Author

This is the messaging I am planning on adding to the docs:

vSphere node driver or custom clusters created prior to v2.9.1 may have resulted in user-data.iso files being orphaned on node deletion. This issue has since been resolved: rancher/rancher#25073, however no automatic cleanup existing for these previously orphaned files. vSphere administrators can manually remove orphaned files, however care should be taken not to remove files in use by existing machines, as this may cause outages for downstream virtual machines.

@jakefhyde jakefhyde self-assigned this Nov 14, 2024
@jakefhyde jakefhyde linked a pull request Dec 17, 2024 that will close this issue
@jakefhyde jakefhyde added this to the v2.11.0 milestone Jan 8, 2025
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