Well, right now, I’ve managed to manually add those rules.
For now, I will assume it was from the RabbitMQ upgrade process I’ve done few
weeks ago. If the issue reappears, I’ll make sure I’ll add a bug report.
Thanks,
Radu
> On Jun 29, 2018, at 3:55 PM, Saverio Proto wrote:
>
> Hello,
>
> I
Hello,
I would suggest to open a bug on launchpad to track this issue.
thank you
Saverio
2018-06-18 12:19 GMT+02:00 Radu Popescu | eMAG, Technology
:
> Hi,
>
> We're using Openstack Ocata, deployed using Openstack Ansible v15.1.7.
> Neutron server is v10.0.3.
> I can see
Hi,
We're using Openstack Ocata, deployed using Openstack Ansible v15.1.7. Neutron
server is v10.0.3.
I can see enable_isolated_metadata and enable_metadata_network only used for
isolated networks that don't have a router which is not our case.
Also, I checked all namespaces on all our novas
Hello Radu,
yours look more or less like a bug report. This you check existing
open bugs for neutron ? Also what version of openstack are you running
?
how did you configure enable_isolated_metadata and
enable_metadata_network options ?
Saverio
2018-06-13 12:45 GMT+02:00 Radu Popescu | eMAG,
Hi all,
So, I'm having the following issue. I'm creating a VM with floating IP.
Everything is fine, namespace is there, postrouting and prerouting from the
internal IP to the floating IP are there. The only rules missing are the rules
to access metadata service:
-A neutron-l3-agent-PREROUTING
