← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1923633] Re: Neutron-tempest-plugin scenario jobs failing due to metadata issues

 

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/796844
Committed: https://opendev.org/openstack/neutron/commit/976cba61331702e1a8e4781af478fa4676afd13d
Submitter: "Zuul (22348)"
Branch:    master

commit 976cba61331702e1a8e4781af478fa4676afd13d
Author: Slawek Kaplonski <skaplons@xxxxxxxxxx>
Date:   Thu Jun 17 15:40:20 2021 +0200

    Force to close http connection after notify about HA router status
    
    Neutron-keepalived-state-change-monitor process is using HTTP to notify
    L3 agent that state of the HA router was changed. It is done through
    unix socket.
    With HTTP 1.1 connection isn't closed properly and if
    router's state was changed more than once in short time, it could happen
    that wsgi worker on the L3 agent's side didn't process second request at
    all. That caused problem with transitioning router to master state after
    creation.
    Request to close connection should be explicitly defined in the header
    [1] and this patch adds "connection: close" header to the headers send in
    such request to do exactly that.
    
    [1] https://www.geeksforgeeks.org/http-headers-connection/
    
    Closes-Bug: #1923633
    Change-Id: Ic08ca5b167db4884efa07112cf9a6c3637e1b827


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

Title:
  Neutron-tempest-plugin scenario jobs failing due to metadata issues

Status in neutron:
  Fix Released

Bug description:
  Since few days all neutron-tempest-plugin-scenario jobs which runs with "ha=True" setting (linuxbridge, openvswitch, openvswitch-iptables_hybrid) are failing often due to failure to authenticate via ssh to the instances.
  From the console log it seems that in every such case there are problems getting metadata from metadata server. Examples of failures:

      https://f237087178b608be7cbc-
  a3abe88e6ab2911093ccea19e77537d0.ssl.cf5.rackcdn.com/785749/1/check
  /neutron-tempest-plugin-scenario-
  linuxbridge/f746672/testr_results.html

  https://5e09181bcc1a50499619-17764b56a5c622705c872e3c7dca2597.ssl.cf2.rackcdn.com/769788/6/check
  /neutron-tempest-plugin-scenario-
  openvswitch/32b4182/testr_results.html

  https://f3719601e38156e4ec26-626e176c8fffa963d6c301ab5a223935.ssl.cf1.rackcdn.com/785633/2/check
  /neutron-tempest-plugin-scenario-
  linuxbridge/4fcd101/testr_results.html

  https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_da7/785895/1/check
  /neutron-tempest-plugin-scenario-
  linuxbridge/da7ea5e/testr_results.html

      https://5b963027deeaf11430aa-
  de753611fe18d17817cd3cc57c427456.ssl.cf1.rackcdn.com/785895/1/check
  /neutron-tempest-plugin-scenario-
  openvswitch/ce74a5b/testr_results.html

  https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_785/785889/3/check
  /neutron-tempest-plugin-scenario-
  openvswitch/785f8bb/testr_results.html

  https://3acd25be4b1698636631-3e445c1a5b8a8c84f71b5a61cff5a09b.ssl.cf5.rackcdn.com/785950/1/check
  /neutron-tempest-plugin-scenario-
  linuxbridge/5c9ea3c/testr_results.html

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


References