Re: [openstack-dev] [neutron][external networks] "neutron net-external-list" returns empty list after restart of neutron-server

The root cause is the same. Could you try the latest code from the trunk and see if problem has gone away? If it has not then it is really a different issue. Thanks, Eugene. On Mon, Jan 6, 2014 at 8:00 PM, rezroo wrote: > Eugene, > Bug 1254555 seems to be the opposite of what I'm observing in

Re: [openstack-dev] [neutron][external networks] "neutron net-external-list" returns empty list after restart of neutron-server

Eugene, Bug 1254555 seems to be the opposite of what I'm observing in Havana devstack. The bug states: " I see that the ext-net network is not available after I do all of the above router/subnet creation. It does become available to tenants as soon as I restart neutron-server." But in the case be

Re: [openstack-dev] [neutron][external networks] "neutron net-external-list" returns empty list after restart of neutron-server

Hi rezoo, This is a known bug for HAavana, which has been fixed (but was not backported), please see: https://bugs.launchpad.net/neutron/+bug/1254555 Thanks, Eugene. On Sun, Jan 5, 2014 at 1:25 AM, rezroo wrote: > Hi all, > I'm testing the Havana devstack and I noticed that after killing and

[openstack-dev] [neutron][external networks] "neutron net-external-list" returns empty list after restart of neutron-server

Hi all, I'm testing the Havana devstack and I noticed that after killing and restarting the neutron server public networks are not returned when queried via horizon or command line, which in Grizzly devstack the query returns the external network even after a quantum-server restart: Basically