VMs cannot mount share in scenario job

Bug #1616115 reported by Rodrigo Barbieri
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Shared File Systems Service (Manila)
Fix Released
High
Rodrigo Barbieri

Bug Description

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 |

Changed in manila:
importance: Undecided → High
Changed in manila:
assignee: nobody → Rodrigo Barbieri (rodrigo-barbieri2010)
status: New → In Progress
Changed in manila:
assignee: Rodrigo Barbieri (rodrigo-barbieri2010) → Ben Swartzlander (bswartz)
Changed in manila:
assignee: Ben Swartzlander (bswartz) → Goutham Pacha Ravi (gouthamr)
Changed in manila:
assignee: Goutham Pacha Ravi (gouthamr) → Rodrigo Barbieri (rodrigo-barbieri2010)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to manila (master)

Reviewed: https://review.openstack.org/359166
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=088747cb7729e2f2b9454f4ae89fd4661e714907
Submitter: Jenkins
Branch: master

commit 088747cb7729e2f2b9454f4ae89fd4661e714907
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: I5bdb70cae4eab2930f3f559a621643ad732909bb

Changed in manila:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/manila 3.0.0.0b3

This issue was fixed in the openstack/manila 3.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.