Instance is allowed to resize to a flavor with lower disk /ram size than that specified in source image, snapshot or backup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
1. Our production environment run with OpenStack Rocky.
2. Steps to reproduce the issue:
(1) Upload an image,e.g: CentOS7, with 10G min_disk and 1024M min_ram specified.
(2) Boot instance with flavor 1-512-5(CPU 1,RAM 512m, Disk 5G) and image CentOS7, then nova raises error telling that flavor 1-512-5 doesn't meet disk/ram requirement specified by CentOS7 image.
(3) Then try to boot instance with flavor 1-1024-10 and image CentOS7 , we'll find it's OK.
(4) Then try to resize the instance to flavor 1-512-5, we will find it's OK and flavor restriction is bypassed.
And consequence caused by this issue is obvious and critical:
In my opinion, the min_disk/min_ram options in image specification serve as a guideline to properly allocate memory/disk and run instance, an inappropriate resize can cause FS corruption and data loss.
tags: | added: resize |
tags: | added: flavor lower |
Changed in nova: | |
assignee: | nobody → pandatt (pandatt) |
Changed in nova: | |
status: | New → Confirmed |
Changed in nova: | |
assignee: | pandatt (pandatt) → nobody |
It's similar with BUG 1707830. /bugs.launchpad .net/nova/ +bug/1707830
https:/