Solve Confidential resizing issue #841
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #841 +/- ##
==========================================
+ Coverage 64.68% 64.81% +0.13%
==========================================
Files 88 88
Lines 8160 8160
Branches 734 734
==========================================
+ Hits 5278 5289 +11
+ Misses 2653 2642 -11
Partials 229 229 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
odesenfans
reviewed
Oct 22, 2025
odesenfans
approved these changes
Nov 3, 2025
… when mounting the base image.
7263032 to
3744af5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related ClickUp, GitHub or Jira tickets : ALEPH-562
Self proofreading checklist
packaging/MakefileChanges
Fix: Solve rootfs resizing issue on confidential instances updating the cloud-init tool version when mounting the base image.
How to test
Create a base confidential image and then create a confidential VM with more rootfs space amount than the original one and check that when the VM runs, it uses all the available space without having to restart the instance.
Notes
Seems a regression issue added on previous cloud-init versions canonical/cloud-init#3036