Lately scenario job started failing. What can be observed is that VMs that mount shares to copy data to them cannot do so. The mount operation fails and it seems there is no connectivity between the VM and the share server.
2016-08-22 22:32:09.057024 | 2016-08-22 22:32:09.056 |
2016-08-22 22:32:09.059106 | 2016-08-22 22:32:09.058 | Captured traceback:
2016-08-22 22:32:09.060927 | 2016-08-22 22:32:09.060 | ~~~~~~~~~~~~~~~~~~~
2016-08-22 22:32:09.062979 | 2016-08-22 22:32:09.062 | Traceback (most recent call last):
2016-08-22 22:32:09.065208 | 2016-08-22 22:32:09.064 | File "tempest/test.py", line 106, in wrapper
2016-08-22 22:32:09.068720 | 2016-08-22 22:32:09.068 | return f(self, *func_args, **func_kwargs)
2016-08-22 22:32:09.070816 | 2016-08-22 22:32:09.070 | File "/opt/stack/new/manila/manila_tempest_tests/tests/scenario/test_share_basic_ops.py", line 202, in test_mount_share_one_vm
2016-08-22 22:32:09.072653 | 2016-08-22 22:32:09.072 | self.mount_share(location, ssh_client)
2016-08-22 22:32:09.075962 | 2016-08-22 22:32:09.074 | File "/opt/stack/new/manila/manila_tempest_tests/tests/scenario/test_share_basic_ops.py", line 354, in mount_share
2016-08-22 22:32:09.078131 | 2016-08-22 22:32:09.077 | "sudo mount.cifs \"%s\" /mnt -o guest" % location
2016-08-22 22:32:09.082595 | 2016-08-22 22:32:09.080 | File "tempest/lib/common/ssh.py", line 168, in exec_command
2016-08-22 22:32:09.088779 | 2016-08-22 22:32:09.088 | stderr=err_data, stdout=out_data)
2016-08-22 22:32:09.096684 | 2016-08-22 22:32:09.095 | tempest.lib.exceptions.SSHExecCommandFailed: Command 'sudo mount.cifs "//10.254.0.25/share-810966c0-d35b-453a-b06f-f682e0dd8b53" /mnt -o guest', exit status: 32, stderr:
2016-08-22 22:32:09.099420 | 2016-08-22 22:32:09.098 | mount error(115): Operation now in progress
2016-08-22 22:32:09.109377 | 2016-08-22 22:32:09.107 | Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
2016-08-22 22:32:09.114994 | 2016-08-22 22:32:09.114 |
2016-08-22 22:32:09.124416 | 2016-08-22 22:32:09.120 | stdout:
2016-08-22 22:32:09.129035 | 2016-08-22 22:32:09.128 |
Reviewed: https:/ /review. openstack. org/359166 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=088747cb772 9e2f2b9454f4ae8 9fd4661e714907
Committed: https:/
Submitter: Jenkins
Branch: master
commit 088747cb7729e2f 2b9454f4ae89fd4 661e714907
Author: Rodrigo Barbieri <email address hidden>
Date: Tue Aug 23 09:25:52 2016 -0300
Fix connectivity problem in Scenario job
In Scenario job, tests consist of VMs mounting shares
provided by share servers.
Admin network is used by share migration tests and is
by default used in other tests as well. Previously it
used the same network address range as tenant networks
(used by VMs) and there was no conflict.
Recently some unknown change broke connectivity between
VMs and share server in scenario job. It seems as there
is now a conflict between those network addresses ranges.
This patch changes the admin network address range,
removing the existing conflict.
Closes-bug: #1616115
Change-Id: I5bdb70cae4eab2 930f3f559a62164 3ad732909bb