volumes are smaller then from flavor described

asked 2017-08-28 09:49:13 -0500

minimike gravatar image

updated 2017-08-28 09:58:07 -0500

hi there

I'm evaluating Debian 9 with OpenStack newton. By creating a new instance, currently I have got the issue that that volumes in cinder are smaller then in the flavor described

openstack flavor show 33ebcd82-7637-4f9f-9939-d32b9804309d
+----------------------------+--------------------------------------+
| Field                      | Value                                |
+----------------------------+--------------------------------------+
| OS-FLV-DISABLED:disabled   | False                                |
| OS-FLV-EXT-DATA:ephemeral  | 0                                    |
| access_project_ids         | None                                 |
| disk                       | 3                                    |
| id                         | 33ebcd82-7637-4f9f-9939-d32b9804309d |
| name                       | small tiny fart                      |
| os-flavor-access:is_public | True                                 |
| properties                 | hw:serial_port_count='1'             |
| ram                        | 256                                  |
| rxtx_factor                | 1.0                                  |
| swap                       |                                      |
| vcpus                      | 1                                    |
+----------------------------+--------------------------------------+

The disk inside the flavor should be 3 GB. The stored image inside glance must be minimal 2 GB. But by creating an instance, they would on Cinder a new volume with only 1 GB created.

That tells my that should be the reason inside my nova-compute.log about why I get "Block Device Mapping is Invalid" messages. But how I could fix it? So that volumes has got by creating a new instance, the right size they I have described inside the flavor in nova before?

2017-08-28 13:55:31.362 4711 WARNING cinder.volume.manager [req-51eb571e-82f1-45f1-bf9b-4c1b3001462d c297cd174a8543c4a42222938c04113d 6ffdbc39228844d5bb12faae0901cb13 - default default] Task 'cinder.volume.flows.manager.create_volume.CreateVolumeFromSpecTask;volume:create' (5ea61113-f94e-4bdf-8251-bfc47cd02688) transitioned into state 'REVERTED' from state 'REVERTING'
2017-08-28 13:55:31.365 4711 WARNING cinder.volume.manager [req-51eb571e-82f1-45f1-bf9b-4c1b3001462d c297cd174a8543c4a42222938c04113d 6ffdbc39228844d5bb12faae0901cb13 - default default] Task 'cinder.volume.flows.manager.create_volume.NotifyVolumeActionTask;volume:create, create.start' (54255bab-9a5b-47c7-bab7-7230e87bc749) transitioned into state 'REVERTED' from state 'REVERTING'
2017-08-28 13:55:31.368 4711 WARNING cinder.volume.manager [req-51eb571e-82f1-45f1-bf9b-4c1b3001462d c297cd174a8543c4a42222938c04113d 6ffdbc39228844d5bb12faae0901cb13 - default default] Task 'cinder.volume.flows.manager.create_volume.ExtractVolumeSpecTask;volume:create' (1ae4efbc-e6c8-466e-aee8-9b6658497d34) transitioned into state 'REVERTED' from state 'REVERTING'
2017-08-28 13:55:31.426 4711 ERROR cinder.volume.flows.manager.create_volume [req-51eb571e-82f1-45f1-bf9b-4c1b3001462d c297cd174a8543c4a42222938c04113d 6ffdbc39228844d5bb12faae0901cb13 - default default] Volume 8fac3a37-ea33-4132-bf87-de529d06ebb0: create failed
2017-08-28 13:55:31.428 4711 WARNING cinder.volume.manager [req-51eb571e-82f1-45f1-bf9b-4c1b3001462d c297cd174a8543c4a42222938c04113d 6ffdbc39228844d5bb12faae0901cb13 - default default] Task 'cinder.volume.flows.manager.create_volume.OnFailureRescheduleTask;volume:create' (5a994d5d-a46e-4992-92d3-dddb4e4d120c) transitioned into state 'REVERTED' from state 'REVERTING'
2017-08-28 13:55:31.431 4711 WARNING cinder.volume.manager [req-51eb571e-82f1-45f1-bf9b-4c1b3001462d c297cd174a8543c4a42222938c04113d 6ffdbc39228844d5bb12faae0901cb13 - default default] Task 'cinder.volume.flows.manager.create_volume.ExtractVolumeRefTask;volume:create' (3f7537aa-0108-4170-80c9-a6e5c961c9f2) transitioned into state 'REVERTED' from state 'REVERTING'
2017-08-28 13:55:31.434 4711 WARNING cinder.volume.manager [req-51eb571e-82f1-45f1-bf9b-4c1b3001462d c297cd174a8543c4a42222938c04113d 6ffdbc39228844d5bb12faae0901cb13 - default default] Flow 'volume_create_manager' (0e3dcce8-52ec-45ed-af47-fbecae5c2c53) transitioned into state 'REVERTED' from state 'RUNNING'
2017-08-28 13:55:31.435 4711 ERROR oslo_messaging.rpc.server [req-51eb571e-82f1-45f1-bf9b-4c1b3001462d c297cd174a8543c4a42222938c04113d 6ffdbc39228844d5bb12faae0901cb13 - default default] Exception during message handling
2017-08-28 13:55:31.435 4711 ERROR oslo_messaging.rpc.server Traceback (most recent call last):
2017-08-28 13:55:31.435 4711 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 133, in _process_incoming
2017-08-28 13:55:31.435 4711 ERROR oslo_messaging.rpc.server     res = self.dispatcher.dispatch(message)
2017-08-28 13:55:31.435 4711 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 150, in dispatch
2017-08-28 13:55:31.435 4711 ERROR oslo_messaging.rpc.server     return self._do_dispatch(endpoint, method, ctxt, args)
2017-08-28 13:55:31.435 4711 ERROR oslo_messaging.rpc.server   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line ...
(more)
edit retag flag offensive close merge delete

Comments

Flavors size ephemeral storage, not volumes. How did you launch the instance, and where does the 1GB volume come from?

Bernd Bausch gravatar imageBernd Bausch ( 2017-08-28 11:21:46 -0500 )edit

Seems you are trying to 'boot from volume' but you are using an image of 2 GB and you are defining a 1GB boot volume. When booting from volume a new Cinder volume is created starting from the chosen Glance image and then it is used as boot volume. It should be bigger than the image size!

Antonio G. gravatar imageAntonio G. ( 2017-08-28 15:56:54 -0500 )edit

Hi

I didn't have defined anything. Only the flavor. How I could configure the size for the boot-volume in cinder by creating a new VM. By using the CLI or Horizon for endusers.

cheers Darko

minimike gravatar imageminimike ( 2017-08-29 04:53:12 -0500 )edit

To boot from a volume, you can create a bootable volume and specify its size. E.g:

openstack volume create --image IMAGE_NAME --size 10 VOLUME_NAME

The UI must be analogous.

Alternatively, there are options in nova boot or openstack server create.

Bernd Bausch gravatar imageBernd Bausch ( 2017-08-29 23:12:50 -0500 )edit