Bug 1533575

Summary:	[RFE][Text] Provide example for mounting options during Node Zero deployment in otopi dialog syntax.
Product:	[oVirt] ovirt-hosted-engine-setup	Reporter:	Nikolai Sednev <nsednev>
Component:	RFEs	Assignee:	Ido Rosenzwig <irosenzw>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bugs, mavital, nsednev, sbonazzo
Target Milestone:	ovirt-4.3.2	Keywords:	EasyFix, FutureFeature, Triaged, UserExperience
Target Release:	---	Flags:	nsednev: needinfo+ sbonazzo: ovirt-4.3? ylavi: planning_ack+ sbonazzo: devel_ack+ rule-engine: testing_ack?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-hosted-engine-setup-2.3.6	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-19 10:03:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nikolai Sednev 2018-01-11 16:36:58 UTC

Description of problem:
Provide example for mounting options during Node Zero deployment.
Currently its not possible to get the right syntax from message "If needed, specify additional mount options for the connection to the hosted-engine storagedomain (example: rsize=32768,wsize=32768) [default is: none]:"
It will be more user friendly to provide an example of mounting options, something like "

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-ha-2.2.3-0.0.master.20171218181916.20171218181911.git4c22b93.el7.centos.noarch
ovirt-hosted-engine-setup-2.2.4-0.0.master.20180109170856.gitb593776.el7.centos.noarch
ovirt-engine-appliance-4.2-20180110.1.el7.centos.noarch


How reproducible:
100%

Steps to Reproduce:
1.Deploy Node Zero over NFS and provide additional mounting options.

Actual results:
Current message does not provide any example of how data should be provided.

Expected results:
An example should provide more understanding of how parameters should be written.

Comment 1 Sandro Bonazzola 2019-01-21 08:28:47 UTC

re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0.
If you think this bug should block 4.3.0 please re-target and set blocker flag.

Comment 2 Ido Rosenzwig 2019-02-17 07:39:40 UTC

Nikolai, I'm not sure what your suggestion was - the last sentence is cut in the middle : "It will be more user friendly to provide...."

Can you please explain what you meant?

Comment 3 Nikolai Sednev 2019-02-17 10:22:21 UTC

(In reply to Ido Rosenzwig from comment #2)
> Nikolai, I'm not sure what your suggestion was - the last sentence is cut in
> the middle : "It will be more user friendly to provide...."
> 
> Can you please explain what you meant?

Yes, the description got somehow unclear and shifted.
I meant for this:
"If needed, specify additional mount options for the connection to the hosted-engine storagedomain:"

It will be more user friendly to provide an example of mounting options, something like "(example: rsize=32768,wsize=32768) [default is: none]"

Please see how it is looking now during interactive deployment:
https://bugzilla.redhat.com/show_bug.cgi?id=1359265#c25

Comment 4 Sandro Bonazzola 2019-02-18 07:54:57 UTC

Moving to 4.3.2 not being identified as blocker for 4.3.1.

Comment 7 Nikolai Sednev 2019-03-06 08:50:29 UTC

If needed, specify additional mount options for the connection to the hosted-engine storagedomain (example: rsize=32768,wsize=32768) []: 

The parentheses are empty, I suppose that it means that default is none.
Works for me on these components:
ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch
ovirt-hosted-engine-setup-2.3.6-1.el7ev.noarch
ovirt-ansible-engine-setup-1.1.8-1.el7ev.noarch
rhvm-appliance-4.3-20190305.1.el7.x86_64
Linux 3.10.0-957.5.1.el7.x86_64 #1 SMP Wed Dec 19 10:46:58 EST 2018 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.6 (Maipo)

Comment 8 Sandro Bonazzola 2019-03-19 10:03:24 UTC

This bugzilla is included in oVirt 4.3.2 release, published on March 19th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.2 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.