Red Hat Bugzilla – Bug 869234
webadmin: we are able to select NFS options on creation of NFS domain V1 with DC=None on 3.0 compatibility
Last modified: 2016-02-10 11:36:50 EST
Created attachment 632033 [details]
Description of problem:
when creating NFS storage domain with 3.0 DC/Cluster/Host when DC=None we can select NFS option MountV4.
the domain will be created as Mount V3 with no error for user.
Version-Release number of selected component (if applicable):
si21.1 upgraded from 3.0
Steps to Reproduce:
1. in a DC/Cluster/Host of 3.0 create a new NFS domain
2. select DC=None, Domain V1, NFS=4
we create the domain as Mount v3 and do not report any error to the user
we should alert the user that mount in 3.0 is V3 only
Additional info: logs
wolf.qa.lab.tlv.redhat.com:/volumes/wolf/Dafna_Data_2_nfs_20120815143626506108 on /rhev/data-center/mnt/wolf.qa.lab.tlv.redhat.com:_volumes_wolf_Dafna__Data__2__nfs__20120815143626506108 type nfs (rw,soft,timeo=600,retrans=6,nosharecache,vers=3,addr=10.35.64.102)
I don't understand the scenario.
Do you mean to say that you start the SD creation with a DC from 3.0 marked, then change it to None?
Or do you mean that you are using for the creation a host that is in a 3.0 DC while the DC=none ?
(In reply to comment #1)
> I don't understand the scenario.
> Do you mean to say that you start the SD creation with a DC from 3.0 marked,
> then change it to None?
> Or do you mean that you are using for the creation a host that is in a 3.0
> DC while the DC=none ?
After discussing with Dafna, afaiu she means that she's creating a domain with DC=none and then attaches it to a 3.0 DC.
While creating the domain you're able to specify the NFS options, but these only take effect if you attach the domain to a 3.1 DC.
In this scenario there is:
1. no warning to user that options will only take effect if domain is attached to a 3.1 DC
2. block the operation in case the host used is not part of a 3.1 DC
(In reply to comment #2)
> After discussing with Dafna, afaiu she means that she's creating a domain
> with DC=none and then attaches it to a 3.0 DC.
> While creating the domain you're able to specify the NFS options, but these
> only take effect if you attach the domain to a 3.1 DC.
> In this scenario there is:
> 1. no warning to user that options will only take effect if domain is
> attached to a 3.1 DC
I wander if a warning is enough, activation may later fail if ignoring the parameters prevent the mount on the SPM
> 2. block the operation in case the host used is not part of a 3.1 DC
This may not solve the issue of moving SDs
> or both.
Why not just prevent this domain to be attached to a 3.0 DC with an error stating why?
Can we reproduce this on 3.3?
reproduce using 3.3 is27
1. create unattached v1 SD with NFS v4
2. create DC 3.0 and attach the SD to it
3. in SD tab choose the relevant SD - appears as v4
4. run mount in host - appears as v3
we are sending v3 instead of v4
Thread-67959::DEBUG::2013-12-17 12:32:40,659::mount::226::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n /bin/mount -t nfs -o soft,nosharecache,timeo=600,ret
rans=6,nfsvers=3 10.35.19.199:/sasha-nfs /rhev/data-center/mnt/10.35.19.199:_sasha-nfs' (cwd None)
Created attachment 837626 [details]
Doesn't look like we'll ever get to this and no customers have complained. If this is important to anyone, feel free to reopen.