Fuel for OpenStack

Too little disk spaces is allocated for cinder

Bug #1494384 reported by Vasily Gorin on 2015-09-10

This bug affects 2 people

	Status	Importance	Assigned to	Milestone
Fuel for OpenStack	Confirmed	Medium	Fuel Sustaining	Fuel for OpenStack 10.0
Mitaka	Won't Fix	Medium	Fuel Python (Deprecated)	Fuel for OpenStack 9.0
Newton	Confirmed	Medium	Fuel Sustaining	Fuel for OpenStack 10.0

Bug Description

Build 288 (RC1)

Scenario:
1. Create new environment
2. Choose Neutron, VLAN
3. Choose Ceph for images
4. Add 1 controller+cinder+ceph
5. Add 2 compute+ceph
6. Add 2 cinder
7. Change disk configuration for both Cinder nodes. Change 'Cinder' volume for vdc
8. Verify networks
9. Deploy the environment

Expected result:
Deployment should be successfully

Actual result:

Deployment failed with following message:

Node 'Untitled (d2:83)' has insufficient disk space
Volume group 'Cinder' requires a minimum of 1536MB

In screenshot we can see Cinder has only 268 mb of disk spaces.

See original description

Tags:

Revision history for this message

Vasily Gorin (vgorin) wrote on 2015-09-10:

screensot Edit (119.0 KiB, image/png)

Revision history for this message

Vasily Gorin (vgorin) wrote on 2015-09-10:

diagnostic snapshot Edit (30.5 MiB, application/octet-stream)

summary:

- Too little memory is allocated for cinder
+ Too little disk spaces is allocated for cinder

Vasily Gorin (vgorin) on 2015-09-10

description:

updated

Revision history for this message

Alexander Gordeev (a-gordeev) wrote on 2015-09-10:

I believe that there are a lot of issues with the current volume manager from nailgun and this one is highly related to it.

also, it's rather fuel-python bug than UI one.

so, feel free to make this bug linked into the following blueprint: https://blueprints.launchpad.net/fuel/+spec/volume-manager-refactoring.

Unfortunately, it couldn't be fixed for 7.0

Vasily Gorin (vgorin) on 2015-09-10

Changed in fuel:
milestone:	7.0 → 8.0
assignee:	Fuel UI Team (fuel-ui) → Fuel Python Team (fuel-python)

Ivan Kliuk (ivankliuk) on 2015-09-11

Changed in fuel:
status:	New → Confirmed

Revision history for this message

Vasily Gorin (vgorin) wrote on 2015-09-11:

There are other steps to reproduce and the same result but for image storage disk spaces.

Scenario:
1. Create new environment
2. Choose Neutron, TUN
3. Choose Ceph for volumes
4. Choose Sahara
5. Choose Ceilometer
6. Add 2 controller+ceph
7. Add 1 controller
8. Add 1 compute
9. Add 3 mongo
10. Change disk configuration for all Mongo nodes. Change 'MongoDB' volume for vdc
11 Deploy env

Expected result: Deployment should be successfully

Actual result:
Deployment failed with following message:
Node 'Untitled (e6:a3)' has insufficient disk space
Volume group 'Image Storage' requires a minimum of 5120MB
It is about nodes from step 6
Only 1804 Mb was allocated for Image Storage.

If it is needed to create new bug report, tell me. I think the reasons of this issue are the same.

Dmitry Pyzhov (dpyzhov) on 2015-10-08

tags:	added: low-hanging-fruit
tags:	removed: low-hanging-fruit

Dmitry Pyzhov (dpyzhov) on 2015-10-22

tags:

added: area-python

Alexander Kislitsky (akislitsky) on 2015-12-28

Changed in fuel:
milestone:	8.0 → 9.0

Dmitry Pyzhov (dpyzhov) on 2016-02-26

tags:

added: module-volumes

Revision history for this message

Bug Checker Bot (bug-checker) wrote on 2016-03-28: Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug