[ostf] size for bootable volume should be no less than image itself

Bug #1406223 reported by Dima Shulyak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
MOS QA Team

Bug Description

By default logic in ostf - default size for bootable volume is set to 1G,
which leads to inability to create a bootable volume with custom images.

Afaik it affects Mellanox team, and probably Sahara team as well, because they are using custom image.

Problem in this code:

https://github.com/stackforge/fuel-ostf/blob/master/fuel_health/nmanager.py#L303

Following code should be tweaked to account image size
https://github.com/stackforge/fuel-ostf/blob/master/fuel_health/nmanager.py#L888-894

Tags: area-ostf
Dima Shulyak (dshulyak)
Changed in fuel:
milestone: none → 6.1
Dmitry Pyzhov (dpyzhov)
tags: added: module-ostf
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

We are lack of resources in 6.1

Changed in fuel:
milestone: 6.1 → 7.0
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → MOS QA Team (mos-qa)
Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Move to invalid, we do not have cases covers bootable volume from other image then cirros. So for now there is not the problem at all

Changed in fuel:
status: Triaged → Invalid
tags: added: area-ostf
removed: module-ostf
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.