Neutron Timeout Errors When Spawning Instances

Solution Verified - Updated -

Issue

  • Instances are spawned into an ERROR state and the following error is generated in the Nova logs:
Request to http://x.x.x.x:9696/v2.0/ports?device_id=aaaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee timed out
  • However, in /var/log/containers/neutron/server.log we see the request completed without error:
2020-09-09 05:55:05.472 58 INFO neutron.wsgi [req-23b8f857-32cc-4551-8eff-0f1ab5f90bcc 76aba00e43ce42849fa863ff634a5164 b7a85cca2a404c1aaf8087f985c3feef - default default] x.x.x.x "GET /v2.0/subnets?id=eeeeeeee-dddd-cccc-bbbb-aaaaaaaaaaaa HTTP/1.1" status: 200  len: 843 time: 37.1405191

Environment

  • Red Hat OpenStack Platform (RHOSP) 13.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content