[Rdo-list] Mitaka: Overcloud installation failed code 6

John Trowbridge trown at redhat.com
Thu Jan 28 16:18:49 UTC 2016 


On 01/28/2016 10:54 AM, John Trowbridge wrote:
> 
> 
> On 01/28/2016 10:31 AM, Ido Ovadia wrote:
>> 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
>>
>> -----------------------------------------------------------------
> 
> First, thanks for trying out RDO Manager!
> 
> I am working on a patch to the image building right now to include ceph.
> The quickstart images currently do not include ceph because I wanted to
> explicitly remove EPEL, but ceph is not yet in one of the CentOS repos.
> I think the plan is to put it in the storage SIG, but in the interim, I
> am patching the image build process to include EPEL only for the ceph
> packages.[1] Sorry this did not make it for the test day. Would you mind
> retrying the deploy without ceph?
> 
> [1] https://review.gerrithub.io/261510

Alternatively, and this would help me verify the patch above could you
do the following from the undercloud (as the stack user) to update the
overcloud-full image and try again:

http://ur1.ca/ogh11


>>
>> _______________________________________________
>> 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