Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1701284

Summary:	[OSP14] Overcloud with Nova NFS backend deployment failure due to InvalidSchemaError
Product:	Red Hat OpenStack	Reporter:	Archit Modi <amodi>
Component:	openstack-tripleo-heat-templates	Assignee:	Martin Schuppert <mschuppe>
Status:	CLOSED ERRATA	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	mburns, mschuppe
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-9.3.1-0.20190314162763.d0a6cb1.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1702892 (view as bug list)		Environment:
Last Closed:	2019-07-02 20:08:28 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1702892

Description Archit Modi 2019-04-18 14:46:43 UTC

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://github.com/openstack/tripleo-heat-templates/commit/393e89bfb6438781d6faaf5dfea2eb468341b451

Steps to reproduce
==================
Include the following params in custom THT:
NovaNfsEnabled: True
NovaNfsShare: "x.x.x.x:/nova/share/path/"

This sets the NovaNfsVersion to '4.2' from the sample-env-generator/sample_values

Expected result
===============
Deployment Succeeds

Actual result
=============
InvalidSchemaError

Environment
===========
1. Queens/Rocky

2. NovaNFS Storage backend

3. Neutron with OVS networking

Logs & Configs
==============
http://paste.openstack.org/show/749486/

Comment 17 errata-xmlrpc 2019-07-02 20:08:28 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2019:1672