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

Bug #1515360 reported by Swaminathan Vasudevan on 2015-11-11
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
High
Unassigned

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.

Gary Kotton (garyk) on 2015-11-18
Changed in neutron:
importance: Undecided → High
status: New → Confirmed
tags: added: needs-attention

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers