[Yahoo-eng-team] [Bug 1832769] [NEW] designate client requires region name to fetch PTR records
Public bug reported: Enable neutron's designate driver to accept the region name as a parameter while making requests. ** Affects: neutron Importance: Undecided Assignee: Mithil Arun (arun-mithil) Status: New ** Changed in: neutron Assignee: (unassigned) => Mithil Arun (arun-mithil) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1832769 Title: designate client requires region name to fetch PTR records Status in neutron: New Bug description: Enable neutron's designate driver to accept the region name as a parameter while making requests. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1832769/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1843801] [NEW] metadata-proxy process stops listening on port 80
Public bug reported: I'm running a metadata agent on provider network and I see that the metadata service stops listening on port 80 randomly. I see that the process itself is running, but port 80 is not open in the DHCP namespace. There are no logs in neutron-server, neutron-metadata- agent, neutron-dhcp-agent or journalctl. The only way to recover is to kill ns-metadata-proxy and have neutron- metadata-agent restart it at which point, the port is up. In addition to monitoring the process itself, neutron-metadata-agent must watch for port 80 in the namespace as well. ENV: Ubuntu 16.04 running neutron rocky. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1843801 Title: metadata-proxy process stops listening on port 80 Status in neutron: New Bug description: I'm running a metadata agent on provider network and I see that the metadata service stops listening on port 80 randomly. I see that the process itself is running, but port 80 is not open in the DHCP namespace. There are no logs in neutron-server, neutron- metadata-agent, neutron-dhcp-agent or journalctl. The only way to recover is to kill ns-metadata-proxy and have neutron- metadata-agent restart it at which point, the port is up. In addition to monitoring the process itself, neutron-metadata-agent must watch for port 80 in the namespace as well. ENV: Ubuntu 16.04 running neutron rocky. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1843801/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1859887] [NEW] External connectivity broken because of stale FIP rule
Public bug reported: Seen a few occurrences of this issue where I have a VM that does not have a FIP attached, but has a port on a tenant network that is attached to an external network via a router. I expect the VM to be able to reach out to the external network, but I see nothing going through. On the VM: --snip-- [root@bob-trove-1 ~]# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever 2: eth0: mtu 1450 qdisc pfifo_fast state UP qlen 1000 link/ether fa:16:3e:97:b3:3b brd ff:ff:ff:ff:ff:ff inet 172.20.7.16/24 brd 172.20.7.255 scope global dynamic eth0 valid_lft 68868sec preferred_lft 68868sec [root@bob-trove-1 ~]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 172.20.7.1 0.0.0.0 UG10000 eth0 169.254.169.254 172.20.7.1 255.255.255.255 UGH 10000 eth0 172.20.2.1920.0.0.0 255.255.255.192 U 10000 eth0 172.20.5.1920.0.0.0 255.255.255.192 U 10000 eth0 172.20.6.0 0.0.0.0 255.255.255.192 U 10000 eth0 172.20.6.64 0.0.0.0 255.255.255.192 U 10000 eth0 172.20.7.0 0.0.0.0 255.255.255.0 U 10000 eth0 --snip-- >From the router namespace: --snip-- root@kvm02:/# ip netns exec qrouter-ea187315-b0c7-4f2e-98e9-128a923fca4e ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: rfp-ea187315-b@if292: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 4e:54:d8:b1:6a:6d brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 169.254.114.242/31 scope global rfp-ea187315-b valid_lft forever preferred_lft forever inet6 fe80::4c54:d8ff:feb1:6a6d/64 scope link valid_lft forever preferred_lft forever 15636: qr-81061dca-85: mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:94:27:37 brd ff:ff:ff:ff:ff:ff inet 192.0.3.1/24 brd 192.0.3.255 scope global qr-81061dca-85 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fe94:2737/64 scope link valid_lft forever preferred_lft forever 15703: qr-41aba180-7f: mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:a5:64:9c brd ff:ff:ff:ff:ff:ff inet 172.20.7.1/24 brd 172.20.7.255 scope global qr-41aba180-7f valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fea5:649c/64 scope link valid_lft forever preferred_lft forever 13957: qr-1408b658-c8: mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:ac:80:c4 brd ff:ff:ff:ff:ff:ff inet 172.20.6.1/26 brd 172.20.6.63 scope global qr-1408b658-c8 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:feac:80c4/64 scope link valid_lft forever preferred_lft forever 11146: qr-127e45c0-8d: mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:82:03:97 brd ff:ff:ff:ff:ff:ff inet 172.20.5.193/26 brd 172.20.5.255 scope global qr-127e45c0-8d valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fe82:397/64 scope link valid_lft forever preferred_lft forever 11147: qr-3ebb2a27-9a: mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:cc:b9:95 brd ff:ff:ff:ff:ff:ff inet 172.20.2.193/26 brd 172.20.2.255 scope global qr-3ebb2a27-9a valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fecc:b995/64 scope link valid_lft forever preferred_lft forever 13970: qr-35480bae-20: mtu 1450 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether fa:16:3e:23:89:f3 brd ff:ff:ff:ff:ff:ff inet 172.20.6.65/26 brd 172.20.6.127 scope global qr-35480bae-20 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fe23:89f3/64 scope link valid_lft forever preferred_lft forever root@kvm02:/# ip netns exec qrouter-ea187315-b0c7-4f2e-98e9-128a923fca4e ip rule 0: from all lookup local 32766: from all lookup main 32767: from all lookup default 36707: from 172.20.7.5 lookup 16 36709: from 172.20.2.248 lookup 16 37304: from 172.20.7.56 lookup 16 46130: from 172.20.7.36 lookup 16 46133: from 172.20.5.223 lookup 16 46134: from 172.20.2.217 lookup 16 46138: from 172.20.2.245 lookup 16 54173: from 172.20.7.16 lookup 16 57482: from 172.20.5.252 lookup 16 62083: from 172.20.7.76 lookup 16 72399: from 172.20.7.80 lookup 16 72454: from 172.20.7.37 lookup 16 2886992577: from 172.20.2.193/26 lookup 2886992577 2886993345: from 172.20.5.19
[Yahoo-eng-team] [Bug 1389694] Re: Unable to list my networks
** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1389694 Title: Unable to list my networks Status in OpenStack Neutron (virtual network service): Invalid Bug description: I am unable to list my external network in PROJECTS>Network->Network Topology But the network is available in Admin section. What is the ISSUE?? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1389694/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1337787] [NEW] Port update crashes when device id does not need to be updated
Public bug reported:
When I call the update_port() method using the ML2 plugin, I see the following
error:
2014-07-04 10:05:40.043 17585 ERROR neutron.api.v2.resource [-]
add_router_interface failed
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource Traceback (most
recent call last):
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource File
"/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py", line 84, in
resource
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource result =
method(request=request, **args)
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource File
"/usr/lib/python2.6/site-packages/neutron/api/v2/base.py", line 185, in
_handle_action
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource return
getattr(self._plugin, name)(*arg_list, **kwargs)
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource File
"/usr/lib/python2.6/site-packages/neutron/services/pn_services/router.py", line
224, in add_router_interface
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource
self.update_port(context, p['id'], port_info)
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource File
"/usr/lib/python2.6/site-packages/neutron/services/pn_services/router.py", line
349, in update_port
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource """
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource File
"/usr/lib/python2.6/site-packages/neutron/db/db_base_plugin_v2.py", line 1397,
in update_port
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource and
(changed_device_id or changed_device_owner)):
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource UnboundLocalError:
local variable 'changed_device_id' referenced before assignment
On further inspection of the file in question (/usr/lib/python2.6/site-
packages/neutron/db/db_base_plugin_v2.py: update_port()), I see that the
variable 'changed_device_id' is only declared within an 'if' condition,
and not otherwise. This causes the crash as a later 'if' tries to read
from it but finds it not declared.
--snip--
def update_port(self, context, id, port):
p = port['port']
changed_ips = False
with context.session.begin(subtransactions=True):
port = self._get_port(context, id)
if 'device_owner' in p:
current_device_owner = p['device_owner']
changed_device_owner = True
else:
current_device_owner = port['device_owner']
changed_device_owner = False
if p.get('device_id') != port['device_id']:
changed_device_id = True
# if the current device_owner is ROUTER_INF and the device_id or
# device_owner changed check device_id is not another tenants
# router
if ((current_device_owner == constants.DEVICE_OWNER_ROUTER_INTF)
and (changed_device_id or changed_device_owner)):
self._enforce_device_owner_not_router_intf_or_device_id(
context, p, port['tenant_id'], port)
--snip--
'changed_device_id' should be set to 'False' by default.
** Affects: neutron
Importance: Undecided
Assignee: Mithil Arun (arun-mithil)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Mithil Arun (arun-mithil)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1337787
Title:
Port update crashes when device id does not need to be updated
Status in OpenStack Neutron (virtual network service):
New
Bug description:
When I call the update_port() method using the ML2 plugin, I see the
following error:
2014-07-04 10:05:40.043 17585 ERROR neutron.api.v2.resource [-]
add_router_interface failed
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource Traceback (most
recent call last):
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource File
"/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py", line 84, in
resource
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource result =
method(request=request, **args)
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource File
"/usr/lib/python2.6/site-packages/neutron/api/v2/base.py", line 185, in
_handle_action
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource return
getattr(self._plugin, name)(*arg_list, **kwargs)
2014-07-04 10:05:40.043 17585 TRACE neutron.api.v2.resource File
"/usr/lib/python2.6/site-packages/neutron/services/pn_services/router.py", line
224, in add_router_interface
2014-07-04 10:05:40.043 17585 TRACE neutron
