Block resize operations that reduce disk capacity
Registered by
Phil Day
Current hypervisors have a range of checks against reduction in disk size for resize operations, ranging from checking root and ephemeral to not checking at all. Because these checks are only implemented at the driver level failures can not be detected by the user (the instance remains active). Resize to a smaller disk can never work if the user already has more data than the new flavor allows - so for consistency any resize to a smaller flavour should be treated as an error.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Phil Day
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
(?)
