yahoo-eng-team team mailing list archive

[OpenStack Infra <1863888@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/708634
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e4de8d0dd3fed2145a309cf2ca7a487f73545af3
Submitter: Zuul
Branch:    master

commit e4de8d0dd3fed2145a309cf2ca7a487f73545af3
Author: Alexandros Soumplis <soumplis@xxxxxxxxxxxxxx>
Date:   Wed Feb 19 14:02:25 2020 +0200

    Improve log message on exception for invalid tunnel type
    
    When a tunnel with an invalid or unsupported type is to be created an
    exception is raised but does not contain info for the offending host.
    Add the host info and tunnel ip address to the exception error message
    for better debugging
    
    Change-Id: Id989f20043c252ff61ab9a6ee227e8c9c7c5029b
    Closes-Bug: #1863888


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  Missing information in log message for Invalid tunnel type

Status in neutron:
  Fix Released

Bug description:
  When a host has an invalid tunnel type, neutron-api raises an error
  like the following:

  2020-02-18 06:25:10.258 1170 ERROR oslo_messaging.rpc.server [req-
  97f7791d-d58d-4315-b7f9-3516f790c46b - - - - -] Exception during
  message handling: neutron_lib.exceptions.InvalidInput: Invalid input
  for operation: Network type value 'gre' not supported.

  This info does not help track the offending host, we need the host
  name and tunnel ip logged.

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