[Yahoo-eng-team] [Bug 1759694] [NEW] DHCP agent doesn't respawn metadata when enable_isolated_metadata and gateway removed

Public bug reported: Hi, We are running Neutron Pike with OVS and DVR. When enable_isolated_metadata is True and we remove the gateway port for a network from a router, a metadata process is not respawned to start serving metadata. How to replicate : [root@5c1fced0888e /]# openstack network cr

[Yahoo-eng-team] [Bug 1746188] [NEW] Virtlogd recreates console.log file as root:root after live migration

Public bug reported: Hi, Description / Steps to reproduce When instances are launched, they get the following console/serial configuration : \n If I look at the permissions for the console.log I see : [root@ nova]

[Yahoo-eng-team] [Bug 1733852] [NEW] Incorrect ARP entries in new DVR routers for Octavia VRRP addresses

Public bug reported: Hi, I am running Ocata Neutron with OVS DVR, l2_population is on, and Ocata Octavia is also installed. Under a certain circumstance, I am getting incorrect ARP entries in the routers for the VRRP address of the loadbalancers created. Here is the ARP table for a router that

[Yahoo-eng-team] [Bug 1696889] [NEW] external_dns_driver causes floating ip association to fail

Public bug reported: If you have 'external_dns_driver = designate' set in neutron.conf and then attempt to associate a floating IP address with an instance, and the instance's network is not present in the 'networkdnsdomains' table, the following error occurs : for field in potential_fields Fil

[Yahoo-eng-team] [Bug 1657597] [NEW] Floating IP association to allowed address pair fails due to transaction in transaction

address_pair_port=allowed_address_port)) File "/usr/lib/python2.7/site-packages/neutron/db/l3_dvr_db.py", line 1073, in update_unbound_allowed_address_pair_port_binding context, address_pair_port['id'], {'port': port_data}) File "/usr/lib/python2.7/site-package

[Yahoo-eng-team] [Bug 1635449] [NEW] Too many pools created from heat template when both listeners and pools depend on a item

Public bug reported: When you deploy a heat template that has both listeners and pools depending on a item, due to the order of locking, you may get additional pools created erroneously. Excerpt of heat template showing the issue : # LOADBALANCERS # test-loadbalancer: type: OS::Ne