← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1456756] [NEW] Could not retrieve gateway port for subnet

 

Public bug reported:

There is this trace at error level in the server logs when DVR is
enabled by default:

[req-179a109e-456a-4743-8395-58b2f322afe2 None None] Could not retrieve
gateway port for subnet {'ipv6_ra_mode': None, 'allocation_pools':
[{'start': u'10.100.0.2', 'end': u'10.100.0.14'}], 'host_routes': [],
'ipv6_address_mode': None, 'cidr': u'10.100.0.0/28', 'id': u'8a47789b-
452d-4ac7-a85b-9e57838456f0', 'subnetpool_id': None, 'name': u'',
'enable_dhcp': True, 'network_id': u'85389a7f-8f50-405c-a19c-
c4ad7b35e9ff', 'tenant_id': u'ec2ad8998456415ea6e8f9a217b5c1d8',
'dns_nameservers': [], 'gateway_ip': u'10.100.0.1', 'ip_version': 4L,
'shared': False}

This is the logstash query:

http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQ291bGQgbm90IHJldHJpZXZlIGdhdGV3YXkgcG9ydCBmb3Igc3VibmV0XCIgQU5EIGJ1aWxkX25hbWU6XCJjaGVjay10ZW1wZXN0LWRzdm0tbmV1dHJvbi1kdnJcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQzMjA2MDU2NzU0MSwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ==

It looks like the trace does not necessarily associated to a failure but
it would be useful to determine why this is happening.

** Affects: neutron
     Importance: Low
         Status: New


** Tags: l3-dvr-backlog

** Changed in: neutron
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1456756

Title:
  Could not retrieve gateway port for subnet

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  There is this trace at error level in the server logs when DVR is
  enabled by default:

  [req-179a109e-456a-4743-8395-58b2f322afe2 None None] Could not
  retrieve gateway port for subnet {'ipv6_ra_mode': None,
  'allocation_pools': [{'start': u'10.100.0.2', 'end': u'10.100.0.14'}],
  'host_routes': [], 'ipv6_address_mode': None, 'cidr':
  u'10.100.0.0/28', 'id': u'8a47789b-452d-4ac7-a85b-9e57838456f0',
  'subnetpool_id': None, 'name': u'', 'enable_dhcp': True, 'network_id':
  u'85389a7f-8f50-405c-a19c-c4ad7b35e9ff', 'tenant_id':
  u'ec2ad8998456415ea6e8f9a217b5c1d8', 'dns_nameservers': [],
  'gateway_ip': u'10.100.0.1', 'ip_version': 4L, 'shared': False}

  This is the logstash query:

  http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQ291bGQgbm90IHJldHJpZXZlIGdhdGV3YXkgcG9ydCBmb3Igc3VibmV0XCIgQU5EIGJ1aWxkX25hbWU6XCJjaGVjay10ZW1wZXN0LWRzdm0tbmV1dHJvbi1kdnJcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTQzMjA2MDU2NzU0MSwibW9kZSI6IiIsImFuYWx5emVfZmllbGQiOiIifQ==

  It looks like the trace does not necessarily associated to a failure
  but it would be useful to determine why this is happening.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1456756/+subscriptions


Follow ups

References