Bug 1800612 - [RFE] NFSv3 for Nova
Summary: [RFE] NFSv3 for Nova
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 13.0 (Queens)
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Lee Yarwood
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-07 14:29 UTC by Jean-Francois Beaudoin
Modified: 2023-03-24 16:58 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-14 13:22:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openstack/tripleo-heat-templates/blob/stable/queens/puppet/services/nova-compute.yaml#L465 0 None None None 2020-07-29 19:57:16 UTC
Red Hat Bugzilla 1650949 0 high CLOSED [OSP13] Add ability to override libvirt NFS mount options for NFS backed Cinder volumes 2022-08-03 16:51:26 UTC

Description Jean-Francois Beaudoin 2020-02-07 14:29:55 UTC 
Description of problem:
Use NFSv3 for Nova volume

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1.use NFSv3
2.
3.

Actual results:
being able to use NFSv3

Expected results:
be able to use NFSv3 for nova volume

Additional info:
We have Heat NovaNfsVersion: but that only accept nfs v4.x and also this option;
parameter_defaults:
  ComputeExtraConfig:
    nova::compute::libvirt::nfs_mount_options: "vers=3,rw,intr,nolock"
the nova mount function has fstype=v4 hardcoded.
Comment 1 Lee Yarwood 2020-02-14 13:22:02 UTC 
NFSv3 is not supported by the block storage or compute services in OSP 13 due to locking issues resolved in NFSv4.

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/advanced_overcloud_customization/storage_configuration#sect-Configuring_NFS_Storage

Closing this out as WONTFIX as a result.
Note You need to log in before you can comment on or make changes to this bug.