openstack stack creation failing during cinder volume creation and disk attachment

asked 2019-10-17 02:30:00 -0600

srini gravatar image

openstack stack create -t create_ca4ci_sec.yaml -e ca4ci_environment.yaml --wait test5 2019-10-17 06:52:55Z [test5]: CREATE_IN_PROGRESS Stack CREATE started 2019-10-17 06:52:55Z [test5.cdlk_instance_zone2_5]: CREATE_IN_PROGRESS state changed 2019-10-17 06:52:56Z [test5.cdlk_instance_zone2_7]: CREATE_IN_PROGRESS state changed 2019-10-17 06:52:58Z [test5.cdlk_instance_zone1_0]: CREATE_IN_PROGRESS state changed 2019-10-17 06:52:59Z [test5.cdlk_instance_zone2_4]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:00Z [test5.cdlk_instance_zone2_9]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:01Z [test5.cdlk_instance_zone2_1]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:02Z [test5.cdlk_instance_zone1_6]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:03Z [test5.cdlk_instance_zone1_9]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:04Z [test5.cdlk_instance_zone1_2]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:05Z [test5.cdlk_instance_zone2_8]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:06Z [test5.cdlk_instance_zone1_4]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:07Z [test5.cdlk_instance_zone1_1]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:08Z [test5.cdlk_instance_zone1_7]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:09Z [test5.cdlk_instance_zone2_2]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:10Z [test5.cdlk_instance_zone1_8]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:11Z [test5.cdlk_instance_zone1_5]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:12Z [test5.cdlk_instance_zone2_3]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:13Z [test5.cdlk_instance_zone1_3]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:14Z [test5.cdlk_instance_zone2_0]: CREATE_IN_PROGRESS state changed 2019-10-17 06:53:15Z [test5.cdlk_instance_zone2_6]: CREATE_IN_PROGRESS state changed 2019-10-17 07:03:00Z [test5.cdlk_instance_zone1_0]: CREATE_FAILED Error: resources.cdlk_instance_zone1_0.resources.group_of_volumes_rook.resources[4].resources.volume_attachment: Failed to attach volume 811754b8-330d-4b10-9814-ec1b09fdef35 to server b82bb288-7ad7-4eaa-af4d-0f8940d85537 - Unexpected API Error. Please rep 2019-10-17 07:03:00Z [test5]: CREATE_FAILED Resource CREATE failed: Error: resources.cdlk_instance_zone1_0.resources.group_of_volumes_rook.resources[4].resources.volume_attachment: Failed to attach volume 811754b8-330d-4b10-9814-ec1b09fdef35 to server b82bb288-7ad7-4eaa-af4d-0f8940d85537 - Unexpect 2019-10-17 07:03:00Z [test5.cdlk_instance_zone2_4]: CREATE_FAILED Error: resources.cdlk_instance_zone2_4.resources.group_of_volumes_rook.resources[1].resources.volume_attachment: Failed to attach volume 2a010060-7948-4b67-9549-b1cdb8489530 to server 5a662f17-b563-4eb2-b1da-0272176f07a7 - Unexpected API Error. Please rep 2019-10-17 07:03:00Z [test5]: CREATE_FAILED Resource CREATE failed: Error: resources.cdlk_instance_zone2_4.resources.group_of_volumes_rook.resources[1].resources.volume_attachment: Failed to attach volume 2a010060-7948-4b67-9549-b1cdb8489530 to server 5a662f17-b563-4eb2-b1da-0272176f07a7 - Unexpect 2019-10-17 07:03:00Z [test5.cdlk_instance_zone2_7]: CREATE_FAILED Error: resources.cdlk_instance_zone2_7.resources.group_of_volumes_rook.resources[1].resources.volume_attachment: Failed to attach volume 52e9b6df-6b39-487a-a671-3c5138fb8975 to server 41e39b53-2d11-4898-8e2f-de003f74374d - Unexpected API Error. Please rep 2019-10-17 07:03:00Z [test5]: CREATE_FAILED Resource CREATE failed: Error: resources.cdlk_instance_zone2_7.resources.group_of_volumes_rook.resources[1].resources.volume_attachment: Failed to attach volume 52e9b6df-6b39-487a-a671-3c5138fb8975 to server 41e39b53-2d11-4898-8e2f-de003f74374d - Unexpect

Stack test5 CREATE_FAILED

^[kroot@ca4ci-cep:/home/cloud-user/digi/orchestration_SEC^[[root@ca4ci-cep /home/cloud-user/digi/orchestration_SEC]# ^M

edit retag flag offensive close merge delete

Comments

There were errors attaching volumes to instances. Check the Nova logs for information why this happened. The Cinder logs may also have relevant information.

I don't see an error message about volume creation, only attachment.

Bernd Bausch gravatar imageBernd Bausch ( 2019-10-17 08:10:08 -0600 )edit

the volumes and servers are created successfully but its failing during attachment? either volume is in reserved state so the attachment is failing any way can we incluede dependency ?

srini gravatar imagesrini ( 2019-10-18 00:35:16 -0600 )edit

| stack_status_reason | Resource UPDATE failed: resources.cdlk_instance_zone1_7: Resource CREATE failed: BadRequest: resources.cdlk_server: Invalid volume: Invalid input received: Invalid volume: Volume 9412c7aa-5847-401a-b70e-1fe340bb7d6f status must be available or downloading (HTTP 400) (Reques

srini gravatar imagesrini ( 2019-10-18 01:07:23 -0600 )edit

I can only say that attachment fails. For details why, check the logs.

According to the Heat message, the volume is not available. Perhaps it's in a state of ERROR, but I can't tell from the data you have shared.

Bernd Bausch gravatar imageBernd Bausch ( 2019-10-18 01:57:58 -0600 )edit