Open Stack

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 not be reflected
inside of the VM via ifconfig or ethtool. It will always show active in
there. So even after we fix bug 1672629, you are going to see the port is
connected inside of the VM.

On Mon, Aug 7, 2017 at 5:21 AM, Volodymyr Litovka <doka.ua at gmx.com> wrote:

> 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 reqs, etc
>
> As people discovered, in Kilo everything was ok - "I have checked the
> behavior of admin_state_up of Kilo version, when port admin-state-up is set
> to False, the port status will be DOWN." - but at least in Ocata it is
> broken.
>
> Anybody facing this problem too? Any ideas on how to work around it?
>
> Thank you.
>
> --
> Volodymyr Litovka
>   "Vision without Execution is Hallucination." -- Thomas Edison
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20170807/0043c3f3/attachment.html>