yahoo-eng-team team mailing list archive

[Rodolfo Alonso <2039038@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The "dhcpclient" spawned in the fullstack tests have a respawn interval
configured. Because of that, when the process is stopped, the
``AsyncProcess._handle_process_error`` method will restart it again, as
seen in the fullstack test logs. For example:
https://paste.opendev.org/show/bG1K9ke8gcRsbjZMDB70/

The ``AsyncProcess._kill_process_and_wait`` has an active wait until the
process is killed, slowing down the test tear down process and
increasing the fullstack CI job time.

This bug is related to https://bugs.launchpad.net/neutron/+bug/2033651.

** Affects: neutron
     Importance: Low
     Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
         Status: New

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

** Changed in: neutron
     Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)

** Changed in: neutron
   Importance: Medium => 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/2039038

Title:
  [fullstack] The "dhclient" kill command can take more than 90 seconds

Status in neutron:
  New

Bug description:
  The "dhcpclient" spawned in the fullstack tests have a respawn
  interval configured. Because of that, when the process is stopped, the
  ``AsyncProcess._handle_process_error`` method will restart it again,
  as seen in the fullstack test logs. For example:
  https://paste.opendev.org/show/bG1K9ke8gcRsbjZMDB70/

  The ``AsyncProcess._kill_process_and_wait`` has an active wait until
  the process is killed, slowing down the test tear down process and
  increasing the fullstack CI job time.

  This bug is related to
  https://bugs.launchpad.net/neutron/+bug/2033651.

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