Ask Your Question
0

cinder volumes attached but not available during OS install

asked 2016-08-03 03:31:58 -0500

MariusPontmercy gravatar image

updated 2016-08-08 10:58:38 -0500

rbowen gravatar image

Hi all,

I just installed Mitaka on three nodes (controller, storage and compute) following this guide http://docs.openstack.org/mitaka/inst...

I stopped at Block Storage Service chapter to have just the basic features before adding complexity.

Everything seems to work fine: I'm able to run instances from ISO images, create cinder volumes, attach them to already running instances (live distros like Cirros), format and mount them, put VMs in network and so on.

The only "glitch" seems to appear when I try to install a non-live distro on a volume starting form a ISO image: both CentOS 7 and Ubuntu 16.04 fail to install for different, yet seemingly related, reasons.

  • CentOS 7 stops install process because Anaconda cannot find any block device available
  • Ubuntu 16.04 stops because, after keyboard and language selection, it says "Your installation CD-ROM cannot be mounted"

These are the logs produced during instance creation:

CONTROLLER NODE

cinder/api.log

[at instance creation]
2016-08-03 03:11:27.244 2680 INFO cinder.api.openstack.wsgi [req-6c15c3e2-bc64-48d6-9a08-3af8402f83d8 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] POST http://osctr01.example.com:8776/v2/c79ea99641814764b377b47e84a40036/volumes
2016-08-03 03:11:27.254 2680 INFO cinder.api.v2.volumes [req-6c15c3e2-bc64-48d6-9a08-3af8402f83d8 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] Create volume of 3 GB
2016-08-03 03:11:27.406 2680 INFO cinder.volume.api [req-6c15c3e2-bc64-48d6-9a08-3af8402f83d8 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] Availability Zones retrieved successfully.
2016-08-03 03:11:28.539 2680 INFO cinder.volume.api [req-6c15c3e2-bc64-48d6-9a08-3af8402f83d8 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] Volume created successfully.
2016-08-03 03:11:28.541 2680 INFO cinder.api.openstack.wsgi [req-6c15c3e2-bc64-48d6-9a08-3af8402f83d8 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] http://osctr01.example.com:8776/v2/c79ea99641814764b377b47e84a40036/volumes returned with HTTP 202
2016-08-03 03:11:28.543 2680 INFO eventlet.wsgi.server [req-6c15c3e2-bc64-48d6-9a08-3af8402f83d8 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] 10.1.6.182 "POST /v2/c79ea99641814764b377b47e84a40036/volumes HTTP/1.1" status: 202  len: 1066 time: 1.3087020
2016-08-03 03:11:28.555 2680 INFO cinder.api.openstack.wsgi [req-3a12c1f8-7403-448a-b030-5e29225552aa 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] GET http://osctr01.example.com:8776/v2/c79ea99641814764b377b47e84a40036/volumes/b63c558f-0d3f-41eb-aacf-2706631c98b1
2016-08-03 03:11:28.887 2680 INFO cinder.volume.api [req-3a12c1f8-7403-448a-b030-5e29225552aa 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] Volume info retrieved successfully.
2016-08-03 03:11:28.895 2680 INFO cinder.api.openstack.wsgi [req-3a12c1f8-7403-448a-b030-5e29225552aa 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] http://osctr01.example.com:8776/v2/c79ea99641814764b377b47e84a40036/volumes/b63c558f-0d3f-41eb-aacf-2706631c98b1 returned with HTTP 200
2016-08-03 03:11:28.897 2680 INFO eventlet.wsgi.server [req-3a12c1f8-7403-448a-b030-5e29225552aa 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] 10.1.6.182 "GET /v2/c79ea99641814764b377b47e84a40036/volumes/b63c558f-0d3f-41eb-aacf-2706631c98b1 HTTP/1.1" status: 200  len: 1239 time: 0.3482981
2016-08-03 03:11:28.909 2680 INFO cinder.api.openstack.wsgi [req-f33a7e5d-0cb3-4905-a1d1-6c4be84deff1 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] GET http://osctr01.example.com:8776/v2/c79ea99641814764b377b47e84a40036/volumes/b63c558f-0d3f-41eb-aacf-2706631c98b1
2016-08-03 03:11:29.160 2680 INFO cinder.volume.api [req-f33a7e5d-0cb3-4905-a1d1-6c4be84deff1 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] Volume info retrieved successfully.
2016-08-03 03:11:29.169 2680 INFO cinder.api.openstack.wsgi [req-f33a7e5d-0cb3-4905-a1d1-6c4be84deff1 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] http://osctr01.example.com:8776/v2/c79ea99641814764b377b47e84a40036/volumes/b63c558f-0d3f-41eb-aacf-2706631c98b1 returned with HTTP 200
2016-08-03 03:11:29.171 2680 INFO eventlet.wsgi.server [req-f33a7e5d-0cb3-4905-a1d1-6c4be84deff1 47959e2d1da143f2bc33b216796e2f4c c79ea99641814764b377b47e84a40036 - - -] 10.1.6.182 "GET /v2/c79ea99641814764b377b47e84a40036/volumes/b63c558f-0d3f-41eb-aacf-2706631c98b1 HTTP/1.1" status: 200  len: 1285 time: 0.2659891
2016-08-03 03:11:39.184 2680 INFO ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-08-10 14:54:39 -0500

You will need to start with a 'cloud enabled' image, such as this Centos image, update it with any additional software or configurations, then create a new image from that running instance with openstack server image create --name NEW_IMAGE_NAME INSTANCE_NAME. There are other methods of creating cloud ready images. You can find more information by consulting this documentation.

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: 2016-08-03 03:31:58 -0500

Seen: 135 times

Last updated: Aug 10 '16