[Rdo-list] Mitaka: Overcloud installation failed code 6
Mike Orazi
morazi at redhat.com
Thu Jan 28 15:44:53 UTC 2016
It looks like the most suspect part of the trace in the pastebin points
to an issue with setting up ceph in particular. Might be worth double
checking ceph specific parameters to see if they look correct.
- Mike
On 01/28/2016 10:40 AM, Sasha Chuzhoy wrote:
> The error code suggests there was a puppet error.
> You can use heat to debug it. It might also be useful to login to the overcloud nodes and check logs.
> Thanks.
>
> Best regards,
> Sasha Chuzhoy.
>
> ----- Original Message -----
>> From: "Ido Ovadia" <iovadia at redhat.com>
>> To: "rdo-list" <rdo-list at redhat.com>
>> Sent: Thursday, January 28, 2016 10:31:05 AM
>> Subject: [Rdo-list] Mitaka: Overcloud installation failed code 6
>>
>> Hello,
>>
>> I deployed Mitaka with rdo-manager on a virtual setup (udercloud, ceph,
>> compute, 3*controller) according to the
>> instructions in https://www.rdoproject.org/rdo-manager/
>>
>> Overcloud deployment failed with code: 6
>>
>>
>> Need some guide to solve this......
>>
>>
>> openstack overcloud deploy --templates --control-scale 3 --compute-scale 1
>> --ceph-storage-scale 1 --ntp-server clock.redhat.com -e
>> /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml
>> -e
>> /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml
>> --libvirt-type qemu
>>
>> .......
>>
>> 2016-01-28 14:22:37
>> [overcloud-ControllerNodesPostDeployment-5b55h3l77m7y-ControllerServicesBaseDeployment_Step2-s72xsdjtuh2a]:
>> CREATE_IN_PROGRESS Stack CREATE started
>> 2016-01-28 14:22:37 [1]: CREATE_IN_PROGRESS state changed
>> 2016-01-28 14:22:37 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:37 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:38 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:38 [ControllerDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:38 [0]: CREATE_IN_PROGRESS state changed
>> 2016-01-28 14:22:38 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:39 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:39 [ControllerDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:39 [NetworkDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:39 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:39 [2]: CREATE_IN_PROGRESS state changed
>> 2016-01-28 14:22:40 [NetworkDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:22:40 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:45 [2]: SIGNAL_IN_PROGRESS Signal: deployment failed (6)
>> 2016-01-28 14:23:46 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:47 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:47 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:47 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:48 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:48 [ControllerDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:49 [NetworkDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:49 [2]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:58 [1]: SIGNAL_IN_PROGRESS Signal: deployment failed (6)
>> 2016-01-28 14:23:58 [1]: CREATE_FAILED Error: resources[1]: Deployment to
>> server failed: deploy_status_code : Deployment exited with non-zero status
>> code: 6
>> 2016-01-28 14:23:59 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:23:59 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:00 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:00 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:01 [ControllerDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:02 [NetworkDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:02 [1]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:15 [0]: SIGNAL_IN_PROGRESS Signal: deployment failed (6)
>> 2016-01-28 14:24:15 [0]: CREATE_FAILED Error: resources[0]: Deployment to
>> server failed: deploy_status_code : Deployment exited with non-zero status
>> code: 6
>> 2016-01-28 14:24:16
>> [overcloud-ControllerNodesPostDeployment-5b55h3l77m7y-ControllerServicesBaseDeployment_Step2-s72xsdjtuh2a]:
>> CREATE_FAILED Resource CREATE failed: Error: resources[2]: Deployment to
>> server failed: deploy_status_code : Deployment exited with non-zero status
>> code: 6
>> 2016-01-28 14:24:16 [0]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:17 [0]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:17 [ControllerServicesBaseDeployment_Step2]: CREATE_FAILED
>> Error: resources.ControllerServicesBaseDeployment_Step2.resources[2]:
>> Deployment to server failed: deploy_status_code: Deployment exited with
>> non-zero status code: 6
>> 2016-01-28 14:24:17 [0]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:18 [ControllerDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:18 [overcloud-ControllerNodesPostDeployment-5b55h3l77m7y]:
>> CREATE_FAILED Resource CREATE failed: Error:
>> resources.ControllerServicesBaseDeployment_Step2.resources[2]: Deployment to
>> server failed: deploy_status_code: Deployment exited with non-zero status
>> code: 6
>> 2016-01-28 14:24:18 [0]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:19 [NetworkDeployment]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:24:19 [0]: SIGNAL_COMPLETE Unknown
>> 2016-01-28 14:28:19 [ComputeNodesPostDeployment]: CREATE_FAILED CREATE
>> aborted
>> 2016-01-28 14:28:19 [overcloud]: CREATE_FAILED Resource CREATE failed:
>> Error:
>> resources.ControllerNodesPostDeployment.resources.ControllerServicesBaseDeployment_Step2.resources[2]:
>> Deployment to server failed: deploy_status_code: Deployment exited with
>> non-zero status code: 6
>> Stack overcloud CREATE_FAILED
>> Deployment failed: Heat Stack create failed.
>>
>> ------------------------------------------------------------------
>>
>> more info
>> =========
>>
>> heat deployment-show 91352911-6df8-4797-be2b-2789b3b5e066 output
>> http://pastebin.test.redhat.com/344518
>>
>> -----------------------------------------------------------------
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>> To unsubscribe: rdo-list-unsubscribe at redhat.com
>>
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe at redhat.com
>
More information about the dev
mailing list