-
Notifications
You must be signed in to change notification settings - Fork 113
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
Automate Major Upgrade Free Space Estimation Updates #7627
Comments
I'd be careful of this one as most system administrators have found out the hard way once allocate space to a drive it is not easy to remove it. LVM makes it easy but if they are not using LVM you have to shrink filesystem, manually respecify the partition boundaries and if you mis type the starting block or end block you can corrupt the entire partition. Often times most places I've worked at it's an unwritten rule to expand but to never shrink a drive due to risks and complexity involved. |
User Story
As an Automate User, I need to have accurate free space estimation for major upgrade migrations. Otherwise, after the migration is done, I may find that I have 0% remaining in /hab, or a few megabytes at best. This creates an emergency situation immediately after the major upgrade.
In particular, for the migration from Elasticsearch to Opensearch in the upgrade to Automate 4.x, the system needs to make sure adequate free space will be available before the upgrade proceeds.
Acceptance Criteria
Definition of Done
The text was updated successfully, but these errors were encountered: