Ask Your Question
0

CentOS 7 packstack - Instance fails, Error: Volume did not finish being created

asked 2017-12-03 02:09:01 -0600

mirza gravatar image

updated 2018-01-05 05:56:18 -0600

Hello there, I installed packstack -allinone on CentOS 7 of openstack ocata. I created a single instance with my manually created image of Lubuntu 16.04. But now i can not create any more instance. Instance creation fails with error -

Build of instance e485ce56-c91c-4a5f-b02a-7a8937264f63 aborted: Volume dbacff49-3263-4728-952d-f4563f70589e did not finish being created even after we waited 3 seconds or 2 attempts. And its status is error.

I have tried with cirros still same problem. But can still start and use the instance of Lubuntu i created with 20GB disk. I have uploaded logs of cinder and nova here - https://www.dropbox.com/s/kokxhq04v6jydzo/logs.tar.gz?dl=0 (https://www.dropbox.com/s/kokxhq04v6j...) . Keep in mind i am a beginner user. Kindly help.

Edit: I can launch instances if i set create new volume to "No". Output of df, pvs and vgs -

[root@localhost mirza]# df
Filesystem              1K-blocks     Used Available Use% Mounted on
/dev/mapper/centos-root 171305296 37026124 125554284  23% /
devtmpfs                  8053972        0   8053972   0% /dev
tmpfs                     8070296    24372   8045924   1% /dev/shm
tmpfs                     8070296     9488   8060808   1% /run
tmpfs                     8070296        0   8070296   0% /sys/fs/cgroup
/dev/sda9                 1038336   235972    802364  23% /boot
/dev/sda8                 1046516     9960   1036556   1% /boot/efi
/dev/loop0                1900368     6148   1772980   1% /srv/node/swiftloopback
tmpfs                     1614060        4   1614056   1% /run/user/42
tmpfs                     1614060       32   1614028   1% /run/user/1000
tmpfs                     1614060        0   1614060   0% /run/user/0
tmpfs                     1614060        0   1614060   0% /run/user/163
[root@localhost mirza]# pvs
  PV         VG             Fmt  Attr PSize    PFree  
  /dev/loop1 cinder-volumes lvm2 a--   <20.60g 612.00m
  /dev/sda10 centos         lvm2 a--  <198.10g      0 
[root@localhost mirza]# vgs
  VG             #PV #LV #SN Attr   VSize    VFree  
  centos           1   2   0 wz--n- <198.10g      0 
  cinder-volumes   1   1   0 wz--n-  <20.60g 612.00m
edit retag flag offensive close merge delete

Comments

1

I use an ipad and can't see your logs, but my guess is that you have no space left for additional volumes. Packstack implements Cinder volumes on an LVM physical volume that resides on a loopback device of a few GB. Run df, pvs or vgs for confirmation.

Bernd Bausch gravatar imageBernd Bausch ( 2017-12-14 18:09:46 -0600 )edit
1

The Horizon instance creation dialog has a flag for volume creation. It's on by default. Reset it and try again; you will then launch an instance whose disk is implemented on ephemeral storage rather than a Cinder volume. That should work if you have no other problems.

Bernd Bausch gravatar imageBernd Bausch ( 2017-12-14 18:13:19 -0600 )edit

Sorry for late reply. I was travelling to another country. There is not enough space here in comment to add output of df, pvs and vgs. I am adding them to the question. One thins is that if i do not create a new volume for a instance it finishes building and i can run it.

mirza gravatar imagemirza ( 2018-01-05 05:32:12 -0600 )edit

I do not see any option to reset the flag in horizon instance creation dialog.

mirza gravatar imagemirza ( 2018-01-05 05:52:06 -0600 )edit

1 answer

Sort by ยป oldest newest most voted
1

answered 2018-01-06 02:32:07 -0600

As I suspected. Only 600MB free space for Cinder volumes:

# vgs
  VG             #PV #LV #SN Attr   VSize    VFree  
  centos           1   2   0 wz--n- <198.10g      0 
  cinder-volumes   1   1   0 wz--n-  <20.60g 612.00m

Since volume sizes are multiples of 1G, you can't create any more volumes.

The option in the instance launch dialog is named "Create New Volume" (I am currently looking at a DevStack based on Queens, but it should be the same on Ocata):

image description

Your solution is to increase the size of the file used for /dev/loop1, or to launch instances without volumes.

edit flag offensive delete link more

Comments

How do i increase size of cinder volume? if i get error by following

[mirza@localhost ~]$ sudo openstack volume list
[sudo] password for mirza: 
Missing value auth-url required for auth plugin password
mirza gravatar imagemirza ( 2018-01-08 03:32:13 -0600 )edit
1

Cinder volumes are created from an LVM volume group. The physical volume of that VG is /dev/loop1. /dev/loop1 is a loopback device based on a 20 GB file.

It is that 20Gb file (I don't know its name) that you need to extend. Not the size of a Cinder volume.

Bernd Bausch gravatar imageBernd Bausch ( 2018-01-08 06:19:42 -0600 )edit

sudo openstack volume list fails because sudo does not inherit the shell variables that contain authentication information. Don't use sudo with the openstack client.

Bernd Bausch gravatar imageBernd Bausch ( 2018-01-08 06:21:58 -0600 )edit

Sorry but can't seem to find how do i extend the 20GB file. I am using one disk with three partitions for my whole setup, one for each of /, /swap, /boot.efi. If you kindly provide me details or provide a link to any article that would be great.

mirza gravatar imagemirza ( 2018-01-14 09:27:44 -0600 )edit

Here is output of losetup

[root@localhost ~]# losetup -a
/dev/loop0: [64768]:3022221 (/srv/loopback-device/swiftloopback)
/dev/loop1: [64768]:7997693 (/var/lib/cinder/cinder-volumes)
mirza gravatar imagemirza ( 2018-01-14 09:27:54 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-12-03 02:09:01 -0600

Seen: 2,129 times

Last updated: Jan 06