yahoo-eng-team team mailing list archive

[OpenStack Infra <1868100@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/713208
Committed: https://git.openstack.org/cgit/openstack/neutron-tempest-plugin/commit/?id=fd4141f2015d25f1b009d7cf2ebdd2907cd8e81a
Submitter: Zuul
Branch:    master

commit fd4141f2015d25f1b009d7cf2ebdd2907cd8e81a
Author: Slawek Kaplonski <skaplons@xxxxxxxxxx>
Date:   Sat Mar 14 14:34:00 2020 +0100

    Fix how nc is called in qos test
    
    We have already nc_listen method in base scenario tests class.
    It was since now used only in port_forwarding tests but we can
    reuse it in QoS tests also.
    
    There was also problem with spawning ncat process, that sometimes,
    without any clear reason for me, process wasn't spawned at all.
    That caused failure of test.
    
    So this patch adds new method ensure_nc_listen() which spawns ncat
    process on remote host and checkes if process is really spawned. That
    way we can avoid problems with not spawned ncat process.
    
    This patch also makes "server" attribute to be optional in nc_listen
    method. It is used only to log console output in case when ssh to the
    server wouldn't work as expected. And if server is not given,
    _log_console_output() method will list all servers which belongs to
    tenant and log console for each of them.
    
    Closes-Bug: #1868100
    
    Change-Id: I54c9f041f2f971219c32005b3fa573c06f0110ef


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

Title:
  ncat process isn't always spawned on guest vm in scenario tests

Status in neutron:
  Fix Released

Bug description:
  Some scenario tests are using ncat process spawned on guest vm to perform some checks.
  It's like that e.g. for port_forwarding and qos tests.
  Recently I found that for unknown for me reason, sometimes "nc" process isn't spawned properly in the guest vm. That causes test failure.

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