Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1846027

Summary: Add timeout to check_connectivity method
Product: Red Hat OpenStack Reporter: Eduardo Olivares <eolivare>
Component: python-neutron-tests-tempestAssignee: Eduardo Olivares <eolivare>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: sclewis
Target Milestone: z2Keywords: AutomationBackLog, Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-neutron-tests-tempest-0.9.0-0.20200622133435.15c85f6.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1859110 1859111 (view as bug list) Environment:
Last Closed: 2020-10-28 15:37:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1859110, 1859111    

Description Eduardo Olivares 2020-06-10 15:34:12 UTC
Description of problem:
Especially for negative tests, when connectivity loss is expected,
allowing the definition of a lower SSH timeout is needed, since default
value of 300 seconds is too high.

This change in 	python-neutron-tests-tempest will be used in tempest_neutron_plugin tests.

The following patch depends on this bug: https://code.engineering.redhat.com/gerrit/#/c/200820/


Version-Release number of selected component (if applicable):
OSP16.1

Comment 1 Eduardo Olivares 2020-06-10 15:41:34 UTC
Fix: https://code.engineering.redhat.com/gerrit/#/c/202945/

Comment 15 errata-xmlrpc 2020-10-28 15:37:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 16.1 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:4284