yahoo-eng-team team mailing list archive

[Armando Migliaccio <1515360@xxxxxxxxxxxxxxxxxx>]

I think the objective here is to add probes with the intention of
removing them, not sure if it's worthwhile tracking this a bug, the
patch will have to be reverted later on.

** Changed in: neutron
       Status: Confirmed => Invalid

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

Title:
  Add more verbose to Tempest Test Errors that causes "SSHTimeout" seen
  in CVR and DVR

Status in neutron:
  Invalid

Bug description:
  Today "SSHTimeout" Errors are seen both in CVR ( Centralized Virtual Routers) and DVR ( Distributed Virtual Routers).
  The frequency of occurence is more on DVR than the CVR.

  But the problem here, is the error statement that is returned and the data that is dumped.
  SSHTimeout may have occured due to several reasons, since in all our tempest test we are trying to ssh to the VM using the public IP ( FloatingIP) 
  1. VM did not come up
  2. VM does not have a private IP address
  3. Security rules in the VM was not applied properly
  4. Setting up of Floating IP
  5. DNAT rules in the Router Namespace.
  6. Scheduling.
  7. Namespace Errors etc.,

  
  We need a way to identify through the tempest test exactly were and what went wrong.

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