Unfortunately Neutron doesn't know anything about the hypervisor to make
that type of call. That will require support in Nova to listen for the port
admin state change from Neutron and reflect it in the loaded hypervisor.
It's worth filing a request with Nova to see if that's something they would
On 8/8/17 7:18 PM, Kevin Benton wrote:
The best way to completely ensure the instance isn't trying to use it
is to detach it from the instance using the 'nova interface-detach'
command.
Sure, but this introduces additional complexity in complex environments
when it's required to have predicta
Once that bug is fixed, the port status will show DOWN in the Neutron API,
but that doesn't affect how it appears inside of the instance.
The best way to completely ensure the instance isn't trying to use it is to
detach it from the instance using the 'nova interface-detach' command.
On Tue, Aug
Hi Kevin,
see below
On 8/8/17 1:06 AM, Kevin Benton wrote:
What backend are you using? That bug is about the port showing ACTIVE
when admin_state_up=False but it's still being disconnected from the
dataplane. If you are seeing dataplane traffic with
admin_state_up=False, then that is a separa
What backend are you using? That bug is about the port showing ACTIVE when
admin_state_up=False but it's still being disconnected from the dataplane.
If you are seeing dataplane traffic with admin_state_up=False, then that is
a separate bug.
Also, keep in mind that marking the port down will still
Hi colleagues,
am I the only who care about this case? -
https://bugs.launchpad.net/neutron/+bug/1672629
The problem is when I set port admin_state_up to False, it still UP on
the VM thus continuing to route statically configured networks (e.g.
received from DHCP host_routes), sending DHCP r
