yahoo-eng-team team mailing list archive

[Salvatore Orlando <1265501@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Failure instance: http://logs.openstack.org/85/64185/1/experimental
/check-tempest-dsvm-neutron-isolated-
parallel/94ca5ac/console.html.gz#_2013-12-27_13_37_15_639

This failure is the 3rd most frequent with parallel testing (after the
error on port quota check and the timeout due to ssh protocol banner
error)

It seems the problem might lie in the fact that the operation, when
neutron is enabled, does not complete in the expected time (which seems
to be 5 seconds for this test).

Possible approaches:
- increase timeout
- enable multiple neutron api workers (might have side effects as pointed out by other contributors)
- address the issue in the nova/neutron interface

** Affects: neutron
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New

** Affects: tempest
     Importance: Undecided
         Status: New


** Tags: neutron-parallel

** Also affects: neutron
   Importance: Undecided
       Status: New

** Also affects: nova
   Importance: Undecided
       Status: New

** Tags added: neutron-parallel

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

Title:
  TestAttachInterfaces fails on neutron w/parallelism

Status in OpenStack Neutron (virtual network service):
  New
Status in OpenStack Compute (Nova):
  New
Status in Tempest:
  New

Bug description:
  Failure instance: http://logs.openstack.org/85/64185/1/experimental
  /check-tempest-dsvm-neutron-isolated-
  parallel/94ca5ac/console.html.gz#_2013-12-27_13_37_15_639

  This failure is the 3rd most frequent with parallel testing (after the
  error on port quota check and the timeout due to ssh protocol banner
  error)

  It seems the problem might lie in the fact that the operation, when
  neutron is enabled, does not complete in the expected time (which
  seems to be 5 seconds for this test).

  Possible approaches:
  - increase timeout
  - enable multiple neutron api workers (might have side effects as pointed out by other contributors)
  - address the issue in the nova/neutron interface

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