yahoo-eng-team team mailing list archive

[OpenStack Infra <1810504@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/628492
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=65a2f86aafa7637ec07aa0a313ea0fae39758608
Submitter: Zuul
Branch:    master

commit 65a2f86aafa7637ec07aa0a313ea0fae39758608
Author: Nate Johnston <nate.johnston@xxxxxxxxxx>
Date:   Fri Jan 4 10:28:01 2019 -0500

    Gracefully handle fetch network fail in qos extend port
    
    When the qos plugin is handling a port resource request through it's
    port resource request extension, sometimes the network a port is
    attached to is looked up and returns None. It may happen like that
    if network will be deleted in concurrent API request.
    
    Change-Id: Ide4acdf4c373713968f9d43274fb0c7550283c11
    Closes-Bug: #1810504


** 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/1810504

Title:
  neutron-tempest-iptables_hybrid job failing with internal server error
  while listining ports

Status in neutron:
  Fix Released

Bug description:
  Example of failed test: http://logs.openstack.org/45/628145/1/gate
  /neutron-tempest-iptables_hybrid/5b37d22/job-
  output.txt.gz#_2019-01-03_19_11_27_801081

  In neutron-server logs there is error like:
  http://logs.openstack.org/45/628145/1/gate/neutron-tempest-
  iptables_hybrid/5b37d22/controller/logs/screen-q-svc.txt.gz?level=ERROR#_Jan_03_19_11_26_174940

  
  There is more examples since last few days: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22line%2069%2C%20in%20list_ports'%5C%22

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