Bug 1597113 - Run VM fails on 'Bad volume specification' when NFS data storage domain path specified using ipv6 address
Summary: Run VM fails on 'Bad volume specification' when NFS data storage domain path ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: General
Version: 4.30.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.2.5
: ---
Assignee: Dan Kenigsberg
QA Contact: Avihai
URL:
Whiteboard:
Depends On:
Blocks: RHEV_IPv6 1403675
TreeView+ depends on / blocked
 
Reported: 2018-07-02 05:36 UTC by eraviv
Modified: 2018-08-09 14:50 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-07-31 15:29:31 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+


Attachments (Terms of Use)
vdsm.log (217.98 KB, text/plain)
2018-07-02 05:36 UTC, eraviv
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 92780 0 master MERGED storage.fileSD: protect mount point name from globbing 2018-07-04 21:58:46 UTC
oVirt gerrit 92823 0 ovirt-4.2 MERGED storage.fileSD: protect mount point name from globbing 2018-07-08 04:15:33 UTC

Description eraviv 2018-07-02 05:36:43 UTC
Created attachment 1455859 [details]
vdsm.log

Description of problem:
Run VM fails on 'Bad volume specification' when NFS data storage domain path specified using ipv6 address.
Storage domain format is V4.

In /lib/python2.7/site-packages/vdsm/storage/fileSD.py+300 the variable volMetaPattern is assigned a glob pattern of the form:
/rhev/data-center/mnt/[2001:db8:ca3:2::1]:_path_to_nfs_dir/<domain_uuid>/images/*/*.meta

and this value is passed to self.oop.glob.glob() on the next line. But the glob function fails to expand the pattern because of the square brackets surrounding the ipv6 address.


Version-Release number of selected component (if applicable):
vdsm-4.30.0-432.git9b70439.el7.x86_64
ovirt-engine 4.3 master git 400aa24

How reproducible:
100%

Steps to Reproduce:
1. connect host to engine using ipv6 address
2. create NFS connectivity from storage to host using ipv6
3. create storage domain on engine specified with ipv6 address path. e.g.
[2001:db8:ca3:2::1]:/path/to/nfs/dir
Note: square brackets are required by engine to specify the ipv6 address
4. create vm on above domain
5. run the VM

Actual results:
VM run is immediately stopped with error message in vdsm+engine logs 'Bad volume specification'

Expected results:
VM should start and reach UP status without errors

Additional info:

Comment 5 Avihai 2018-07-16 10:53:53 UTC
Verified on 4.2.5.2_SNAPSHOT-76.g2d45cde.0.scratch.master.el7ev.

Comment 6 Sandro Bonazzola 2018-07-31 15:29:31 UTC
This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.5 release, it has been closed with a resolution of CURRENT RELEASE.

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


Note You need to log in before you can comment on or make changes to this bug.