Bug 1967995

Summary:	volume/snaphshot tests timing out test_snapshot_pattern, test_volume_boot_pattern
Product:	Red Hat OpenStack	Reporter:	wes hayutin <whayutin>
Component:	openstack-nova	Assignee:	OSP DFG:Compute <osp-dfg-compute>
Status:	CLOSED DUPLICATE	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	16.2 (Train)	CC:	dasmith, eglynn, jhakimra, kchamart, sbauza, sgordon, vromanso
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-07 12:53:52 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:

Description wes hayutin 2021-06-04 16:41:55 UTC

Description of problem:

skipping these tests.. this bug documents the skip of this test and allows for further debug if needed.  This may not be a consistent error.

tempest.scenario.test_snapshot_pattern.TestSnapshotPattern.test_snapshot_pattern
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern

both timed out.

https://sf.hosted.upshift.rdu2.redhat.com/logs/94/211494/41/check/periodic-tripleo-ci-rhel-8-scenario001-standalone-rhos-16.2/82d0690/logs/undercloud/var/log/tempest/stestr_results.html

More investigation and determining if the failure is consistent is required.

Comment 1 Kashyap Chamarthy 2021-06-07 09:02:28 UTC

Hi, Wes.  A meta-comment:

It's hard to tell just from the time-out failure whether it's consistent or not :-)  Do add a comment here if you're seeing these two tests fail more consistently...

---------------------------------------------------------------------------------------
[...]
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/ssh.py", line 113, in _get_ssh_connection
    sock=proxy_chan)
  File "/usr/lib/python3.6/site-packages/paramiko/client.py", line 362, in connect
    raise NoValidConnectionsError(errors)
paramiko.ssh_exception.NoValidConnectionsError: [Errno None] Unable to connect to port 22 on 192.168.24.108

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/tempest/common/utils/__init__.py", line 90, in wrapper
    return f(*func_args, **func_kwargs)
  File "/usr/lib/python3.6/site-packages/tempest/scenario/test_snapshot_pattern.py", line 83, in test_snapshot_pattern
    server=server_from_snapshot)
  File "/usr/lib/python3.6/site-packages/tempest/scenario/manager.py", line 939, in get_timestamp
    username=username)
  File "/usr/lib/python3.6/site-packages/tempest/scenario/manager.py", line 638, in get_remote_client
    linux_client.validate_authentication()
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/utils/linux/remote_client.py", line 59, in wrapper
    six.reraise(*original_exception)
  File "/usr/lib/python3.6/site-packages/six.py", line 675, in reraise
    raise value
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/utils/linux/remote_client.py", line 32, in wrapper
    return function(self, *args, **kwargs)
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/utils/linux/remote_client.py", line 115, in validate_authentication
    self.ssh_client.test_connection_auth()
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/ssh.py", line 217, in test_connection_auth
    connection = self._get_ssh_connection()
  File "/usr/lib/python3.6/site-packages/tempest/lib/common/ssh.py", line 129, in _get_ssh_connection
    password=self.password)
tempest.lib.exceptions.SSHTimeout: Connection to the 192.168.24.108 via SSH timed out.
User: cirros, Password: None
[...]
---------------------------------------------------------------------------------------

Comment 2 Kashyap Chamarthy 2021-06-07 12:53:52 UTC

Closing this as a dupe (thanks, Lee Yarwood for the pointer on IRC).

*** This bug has been marked as a duplicate of bug 1965897 ***

Comment 3 Red Hat Bugzilla 2023-09-18 00:27:18 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days