o:* Steve Powell <spow...@silotechgroup.com>; Chris Sarginson <
csarg...@gmail.com>; openstack-operators@lists.openstack.org
*Subject:* Re: [Openstack-operators] Neutron Issues
I think you probably need to say what ML2 mechanism driver(s) you are using.
On Tue, May 2, 2017 at
gt; *Sent:* Tuesday, May 2, 2017 5:24 PM
> *To:* Steve Powell <spow...@silotechgroup.com>;
> openstack-operators@lists.openstack.org
> *Subject:* Re: [Openstack-operators] Neutron Issues
>
>
>
> If you're using openvswitch, with Newton there was a change to the default
&
rabbit]
>
>
>
> [oslo_messaging_zmq]
>
>
>
> [oslo_middleware]
>
> enable_proxy_headers_parsing = True
>
> enable_http_proxy_to_wsgi = True
>
>
>
> [oslo_policy]
>
>
>
> [qos]
>
>
>
> [quotas]
&g
Failed to allocate networks usually means that the port failed to bind on
the neutron side.
If you're using ML2 + (ovs or Linux bridge), that's usually caused by
either the agent on the host being dead, or there being no agent running on
that host at all.
Do a 'neutron agent-list' and ensure
Hello Ops!
I have a major issue slapping me in the face and seek any assistance possible.
When trying to spin up and instance whether from the command line, manually in
Horizon, or with a HEAT template I receive the following error in nova and,
where applicable, heat logs:
Failed to allocate
