Ask Your Question
0

Devstack fails instance creation other than tiny

asked 2017-08-23 07:05:53 -0600

Georgios gravatar image

Hi Team, I have devstack install in a server. I ma trying to test a debian image, however when I am launching the image it fails with the below error:

Error: Failed to perform requested operation on instance "Test Debian", the instance has an error status: Please try again later [Error: Build of instance 1ca911c8-5b25-481b-8a91-a95dd264bbe5 aborted: Volume 709f8de6-787b-4002-9857-44562ebe561c did not finish being created even after we waited 0 seconds or 1 attempts. And its status is error.].

I tried to change the scheduling and ram ratio but no success. the problem is there regardless the Linux as I tested also with Cirros medium and the problem is the same.

On the other hand I can launch a cirros tiny image without a problem.

However with 2 or more even tiny I am getting the following issue again:

Error: Failed to perform requested operation on instance "Cisrros-2", the instance has an error status: Please try again later [Error: Build of instance 981574c3-944a-4ea4-9f65-e1d9101836eb aborted: Volume c57a09ca-d4d9-4325-9316-b1c498f3949e did not finish being created even after we waited 0 seconds or 1 attempts. And its status is error.].

Can you please advice where to look in order to correct the issue?

edit retag flag offensive close merge delete

Comments

From the error, it seems it is related to a volume problem (try checking if you have enough available disk space). Have you found any interesting error in Cinder logs?

Antonio G. gravatar imageAntonio G. ( 2017-08-24 16:40:00 -0600 )edit

Hi Antonio,I will try to redeploy the devstack again and retry. In another case when I created a debian volume and then the VM it looks that worked, but only once, then went back to this situation.

Georgios gravatar imageGeorgios ( 2017-08-25 01:15:37 -0600 )edit

Problem persists, any idea on the logs Also is there a limitation that prohibits sizes to be created?

Georgios gravatar imageGeorgios ( 2017-08-25 03:08:05 -0600 )edit

Hi Georgios, please paste your cinder log files.

Antonio G. gravatar imageAntonio G. ( 2017-08-28 15:47:23 -0600 )edit

I past the logs, link: http://paste.openstack.org/show/619744/ I redeployed devstack and the problem persists. Now I have a new issue....

Georgios gravatar imageGeorgios ( 2017-08-29 05:57:12 -0600 )edit

1 answer

Sort by » oldest newest most voted
1

answered 2017-09-02 18:19:20 -0600

Georgios gravatar image

hi TEAM!!

I am writing the below guide for those that might had the same issue with me when the CINDER faces problems with space:

  1. Create an image storage, https://stackoverflow.com/questions/257844/quickly-create-a-large-file-on-a-linux-system (reference Link) Command: fallocate -l 30G /media/project0001.img

  2. Modifying the amount of loopback devices [reference link] (http://www.anthonyldechiaro.com/blog/2010/12/19/lvm-loopback-how-to/ (http://www.anthonyldechiaro.com/blog/...)) To see all the loopback devices: Command: ls -l /dev/loop

In case you need to add new loopback devices, If loopback support is compiled as a module: Command: modprobe loop max_loop=64

To make permanent edit /etc/modules or /etc/modprobe.conf and use add one of the following: loop max_loop=64 options loop max_loop=64

If loopback module is compiled into the kernel you will need to reboot, edit the kernel command-line parameters appending ‘max_loop=64’ to the end.

  1. Check the Volume Group
    Command: vgs output should be like the below:
    VG #PV #LV #SN Attr VSize VFree
    stack-volumes-default 1 0 0 wz--n- 10.01g 10.01g
    stack-volumes-lvmdriver-1 2 9 1 wz--n- 40.00g 31.00g

  2. Check the avaialble loopback devices
    Command: pvscan
    PV /dev/loop1 VG stack-volumes-lvmdriver-1 lvm2 [10.01 GiB / 10.01 GiB free]
    PV /dev/loop0 VG stack-volumes-default lvm2 [10.01 GiB / 10.01 GiB free]
    Total: 2 [20.02 GiB] / in use: 2 [20.02 GiB] / in no VG: 0 [0 ]

Means we can use loop3 up to the maximum number of loop<#>

  1. Link the image with a loopback storage device

    Command: losetup /dev/loop<the number you have created> /media/projecct0001.img

5.Extend the volume group stack-volumes-lvmdriver-1 Command:lvm vgextend "stack-volumes-lvmdriver-1" /dev/loop0 WARNING: dos signature detected on /dev/loop2 at offset 510. Wipe it? [y/n]: y <--Reply y Wiping dos signature on /dev/loop2. Physical volume "/dev/loop2" successfully created

  1. Check the extension Command: vgs
    VG #PV #LV #SN Attr VSize VFree
    stack-volumes-default 1 0 0 wz--n- 10.01g 10.01g
    stack-volumes-lvmdriver-1 4 0 0 wz--n- 100.00g 100.00g
edit flag offensive delete link more

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-08-23 07:05:53 -0600

Seen: 3,054 times

Last updated: Sep 02 '17