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

Bug 1478854

Summary:	Edit Host/Kernel dialog should not accept blank char as value for Kernel command line
Product:	[oVirt] ovirt-engine	Reporter:	Jiri Belka <jbelka>
Component:	Frontend.WebAdmin	Assignee:	Dominik Holler <dholler>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.1.5.1	CC:	bugs, dholler, lleistne, mburman, rbarry, tjelinek
Target Milestone:	ovirt-4.3.1	Flags:	tjelinek: ovirt-4.3? tjelinek: planning_ack? rule-engine: devel_ack+ lleistne: testing_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.1.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-13 16:39:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jiri Belka 2017-08-07 10:36:55 UTC

Description of problem:

blank char (whitespace) is accepted as value for Kernel command line in Edit Host/Kernel dialog. This causes options which can be (un)checked being disabled. It's not obvious there's whitespace in Kernel command line field.

Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-4.1.5.1-0.1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. open Edit Host/Kernel dialog
2. click in Kernel command line and make whitespace
3. click ok

Actual results:
whitespace is accepted as value and this causes other "features" being disabled

Expected results:
blank char is not real value

Additional info:

Comment 1 Dominik Holler 2018-10-03 08:21:48 UTC

On verification, please ensure that adding NFS data domain via web UI is still working, thanks.

Comment 2 Ryan Barry 2019-01-21 14:53:42 UTC

Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both

Comment 3 samuel macko 2019-02-13 13:47:49 UTC

We don't have a proper build right now, please move to ON_QA when 4.3.1 will be available for QE.

Comment 4 Michael Burman 2019-03-07 10:02:39 UTC

Verified on - rhvm-4.3.2-0.1.el7.noarch

Comment 5 Sandro Bonazzola 2019-03-13 16:39:30 UTC

This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

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