Open Stack

Your email subject seems to indicate that you found this error in a Neutron
log. I don't think this is correct; in my experience, the error is raised
by nova-compute because it has not received the confirmation from Neutron
that the network structures on the compute node are ready.

It can be due to a loop in the OVS agent, but there may be other reasons. I
would check for matching Neutron error logs.

Bernd.

On Thu, Feb 23, 2023 at 10:14 PM Adivya Singh <adivya1.singh at gmail.com>
wrote:

> Hi Team,
>
> I get these error not often , but some times
>
>  Went to status ERROR due to \"Message: Build of instance
> 6072c3e9-e530-4173-93b0-4338d6651ade aborted: Failed to allocate the
> network(s), not rescheduling., Code: 500\"\n2023-02-20 16:32:07Z
> [activelogic]: CREATE_FAILED  ResourceInError: resources.activelogic: Went
> to status ERROR due to \"Message: Build of instance
> 356868a0-7341-43e4-8711-58d633fd745b aborted: Failed to allocate the
> network(s), not rescheduling
>
> My initial thought was these errors related to OVS switch as it goes in
> some kind of a loop while creating a instance, Any thought on this
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230223/e5073327/attachment.htm>