Hi all,
Thanks for the quick response.
Reason for the issue was I was not using admin privileged user to create
router, that attached to a external(provider) network. So the user was able
to form a network but not able connect to external network.
I think there should be some exception generatio
On 27 Feb 2017, at 15:10, Turbo Fredriksson wrote:
> Are you possibly using distributed routers? There’s a bug (somewhere) that
> made Newton
> break when using floating IPs with distributed routers.
These are the two issues I know that is/might be related:
https://bugs.launchpad.net/n
On 27 Feb 2017, at 14:10, Amit Uniyal wrote:
> Issue : I tried to attach floating ip to a VM, it attached but its not
> accessible from from outside.
Are you possibly using distributed routers? There’s a bug (somewhere) that made
Newton
break when using floating IPs with distributed routers.
t;openstack@lists.openstack.org<mailto:openstack@lists.openstack.org>"
mailto:openstack@lists.openstack.org>>
Subject: [Openstack] Newton FloatingIP issue - attached but not accessible
Hi all,
Issue : I tried to attach floating ip to a VM, it attached but its not
accessible from from
Amit,
I'm still new to OpenStack, but for what it's worth, this sounds like maybe
an issue with the router between the private network where your VM is
running and the network from where you're getting the floating IP. You
might try double checking that.
On Mon, Feb 27, 2017 at 8:10 AM, Amit Un
Hi all,
Issue : I tried to attach floating ip to a VM, it attached but its not
accessible from from outside.
For admin project its working fine, successfully attached and also
available from outside via floating IP. But for other project its able to
attach but no accessible.
I have tried to chec
