Overcloud with Nova NFS backend deployment failure due to InvalidSchemaError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Martin Schuppert |
Bug Description
Description
===========
Due to a recent change [0] in storage.yaml, NovaNfsVersion is set to '4.2' if not set by user. There is an InvalidSchemaError when this yaml is validated, since it doesn't take the value as a string.
[0] https:/
Steps to reproduce
==================
Include the following params in custom THT:
NovaNfsEnabled: True
NovaNfsShare: "x.x.x.
This sets the NovaNfsVersion to '4.2' from the sample-
Expected result
===============
Deployment Succeeds
Actual result
=============
InvalidSchemaError
Environment
===========
1. Queens/Rocky
2. NovaNFS Storage backend
3. Neutron with OVS networking
Logs & Configs
==============
http://
This is only an issue with the sample file. Can be worked around with setting NovaNfsVersion in quotes in an environment file:
NovaNfsVersion: "4.2"
Fixes proposed /review. openstack. org/#/c/ 653720/ /review. openstack. org/653721 /review. openstack. org/653722
Master: https:/
Rocky: https:/
Queens: https:/