Ask Your Question
0

Volume Creation Issue: Hangs in creating

asked 2015-02-07 16:24:20 -0500

hckeyguy33 gravatar image

I've been attempting to create volumes on the block storage node. I've actually had this working once however when I restarted the controller everything went haywire. I've since gone through another complete reinstall to the block storage point and still have this same issue. I've read some of the other posts regarding this but they either haven't been answered or I didn't show a similar issue in the logs. From what I can tell cinder thinks everything went through fine.

Problem: When running the verify sequence "cinder create --display-name demo-volume1 1" subsequently it never creates the volume in the lvm cinder-volumes. It also shows indefinitely as "creating" in the cinder list command. I can manually go into the cinder-volumes volume group and manually create a logical volume within it fine using lvcreate. However cinder seems unable to create the volume itself.

Note: I'm running Centos 7 w/ Openstack Juno


cinder-manage service list (on both controller and storage) Binary Host Zone Status State Updated At cinder-scheduler controller nova enabled :-) 2015-02-07 21:56:33 cinder-volume storage nova enabled :-) 2015-02-07 21:56:32


vgdisplay (on storage) No device found for PV q0T2vH-xdkZ-lVlc-fznp-M3n8-bjC8-rHuT7v. --- Volume group --- VG Name cinder-volumes System ID
Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 36.38 TiB PE Size 4.00 MiB Total PE 9536741 Alloc PE / Size 2 / 8.00 MiB Free PE / Size 9536739 / 36.38 TiB VG UUID XwasvW-gADN-y9Ox-3uyH-hKjI-oGCU-reFD1d


lvdisplay (on storage to show other lv's created, I've manually created these even though they show up in the cinder list) No device found for PV q0T2vH-xdkZ-lVlc-fznp-M3n8-bjC8-rHuT7v. --- Logical volume --- LV Path /dev/cinder-volumes/dem3 LV Name dem3 VG Name cinder-volumes LV UUID Yie3bu-5lek-QxRt-gfjc-BY4Z-qyB2-BoFMIG LV Write Access read/write LV Creation host, time storage, 2015-02-07 16:40:07 -0500 LV Status available # open 0 LV Size 4.00 MiB Current LE 1 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:8

--- Logical volume --- LV Path /dev/cinder-volumes/dem LV Name dem VG Name cinder-volumes LV UUID 2cznOu-3Mzj-VlnM-uiMh-ntMV-0flo-FviDTQ LV Write Access read/write LV Creation host, time storage, 2015-02-07 16:41:07 -0500 LV Status available # open 0 LV Size 4.00 MiB Current LE 1 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:9


cinder list (on storage and controller, dem2 was seeing what the scheduler would say if the storage node was down) +--------------------------------------+----------+--------------+------+-------------+----------+-------------+ | ID | Status | Display Name | Size | Volume Type | Bootable | Attached to | +--------------------------------------+----------+--------------+------+-------------+----------+-------------+ | 7f947979-77dd-44ca-9da4-24409fdeca82 | creating | demo-volume1 | 1 | None | false | | | 83dc36ab-9a28-4b9d-952b-ca39dc8815b3 | error | dem2 | 1 | None | false | | | bfd3aa9f-9022-4a0f-8c20-4b11380c623d | creating | dem | 1 | None | false | | | d10de795-0ec3-41cb-b048-f3b78bd7ff41 | creating | dem3 | 1 | None | false | | +--------------------------------------+----------+--------------+------+-------------+----------+-------------+


My latest run cinder create --display-name forquestion 2 +---------------------+--------------------------------------+ | Property | Value | +---------------------+--------------------------------------+ | attachments | [] | | availability_zone | nova | | bootable | false | | created_at | 2015-02-07T22:01:33.677857 | | display_description | None | | display_name | forquestion | | encrypted | False | | id | 96c82a50-a96b-41d2-bff6-2be111b214c9 | | metadata | {} | | size ...

(more)
edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
1

answered 2015-02-11 19:01:56 -0500

hckeyguy33 gravatar image

I'm not sure this is so much an answer (because I can't verify it as an answer) but what I've done to resolve.

1) Having a feeling there was a corrupted DB I reinstalled the controller node from scratch (thank goodness for pxebooting :))

2) I also removed from my /etc/hosts file any indication for localhost and my hostname to 127.0.0.1. It now only resolves to my management IP.

Between the two it seems to work now, I've also rebooted the system to see it come up correctly and it has.

edit flag offensive delete link more
0

answered 2015-02-10 06:54:56 -0500

I have exactly the same problem some sugestion?

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: 2015-02-07 16:22:36 -0500

Seen: 544 times

Last updated: Feb 11 '15