Hi Anda,

some things you could check:

Do you have 2 networks on director (ctlplane and external) and are they reachable from the overcloud nodes?

Seems to me that you have network issues and that's because you're seeing those long timeouts.

For "Message: No valid host was found. There are not enough hosts available" message you could check "/var/log/nova/nova-conductor.log".

Regards


On Wed, Jan 31, 2018 at 10:14 AM, Anda Nicolae <anicolae@lenovo.com> wrote:
I've let the deployment run overnight and it failed after almost 4hrs with the errors below. Do you happen to know the config file where I can decrease the timeout? I looked in /etc/nova/nova.conf and in ironic config files but I couldn't find anything relevant.

The errors are:

[overcloud.Compute.0]: CREATE_FAILED  ResourceInError: resources[0].resources.NovaCompute: Went to status ERROR due to "Message: Unknown, Code: Unknown"
[overcloud.Controller.0]: CREATE_FAILED  Resource CREATE failed: ResourceInError: resources.Controller: Went to status ERROR due to "Message: No valid host was found. There are not enough hosts available., Code: 500"

It is unclear to me why the above errors occur, since in my instackenv.json I declared node capabilities for both the computer and the controller node to be greater than the compute and controller flavors from 'openstack flavor list'.

However, I've found this link and I am looking over it:
https://docs.openstack.org/ironic/latest/admin/troubleshooting.html#nova-returns-no-valid-host-was-found-error

Thanks,
Anda

-----Original Message-----
From: Raoul Scarazzini [mailto:rasca@redhat.com]
Sent: Tuesday, January 30, 2018 8:17 PM
To: Anda Nicolae; users@lists.rdoproject.org
Subject: Re: [rdo-users] RHOSP 10 failed overcloud deployment

On 01/30/2018 04:39 PM, Anda Nicolae wrote:
> Got it.
>
> I've noticed that it spends quite some time in CREATE_IN_PROGRESS state for OS::Heat::ResourceGroup resource (on Controller node).
> Overcloud deployment fails after 4h. I will check in which config file is the overcloud deployment timeout configured and decrease it.
>
> Thanks,
> Anda

Check also network settings. 4h timeout is the default when something is unreachable.

--
Raoul Scarazzini
rasca@redhat.com
_______________________________________________
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscribe@lists.rdoproject.org