yahoo-eng-team team mailing list archive

[Salvatore Orlando <1261559@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In some instances, tempest scenario tests fail with a timeout error
similarly to bug 1253896, but unlike other occurrences of this bug, the
failure happens even if all the elements connecting the floating IP to
the VM are properly wired.

Further investigations revealed the a DHCPDISCOVER is apparently not sent from the VM.
An instance of this failure can be seen here: http://logs.openstack.org/60/58860/2/gate/gate-tempest-dsvm-neutron/b9b25eb

Looking at syslog for this tempest run, only one DHCPDISCOVER is
detected, even if 27 DHCPRELEASE are sent (thus meaning the
notifications were properly handled and the dnsmasq processed were up
and running).

Relevant events from a specific failure (boot_volume_pattern)

Server boot: 15:18:44.972
Fip create: 15:18:45.075
Port wired: 15:18:45.279
Fip wired: 15:18:46:356
Server delete: 15:22:03 (timeout expired)

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Timeouts due to VMs not sending DHCPDISCOVER messages

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  In some instances, tempest scenario tests fail with a timeout error
  similarly to bug 1253896, but unlike other occurrences of this bug,
  the failure happens even if all the elements connecting the floating
  IP to the VM are properly wired.

  Further investigations revealed the a DHCPDISCOVER is apparently not sent from the VM.
  An instance of this failure can be seen here: http://logs.openstack.org/60/58860/2/gate/gate-tempest-dsvm-neutron/b9b25eb

  Looking at syslog for this tempest run, only one DHCPDISCOVER is
  detected, even if 27 DHCPRELEASE are sent (thus meaning the
  notifications were properly handled and the dnsmasq processed were up
  and running).

  Relevant events from a specific failure (boot_volume_pattern)

  Server boot: 15:18:44.972
  Fip create: 15:18:45.075
  Port wired: 15:18:45.279
  Fip wired: 15:18:46:356
  Server delete: 15:22:03 (timeout expired)

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