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

Bug 1674214

Summary: Kernel command line does not allow spaces
Product: [oVirt] ovirt-engine Reporter: Ryan <ryan>
Component: Frontend.WebAdminAssignee: Ryan Barry <rbarry>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: bugs, mburman, rbarry
Target Milestone: ovirt-4.3.1Flags: rule-engine: ovirt-4.3+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 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 Ryan 2019-02-09 22:26:52 UTC 
Description of problem:
After updating the engine to 4.3 if you edit or add a host and attempt to set multiple kernel command line options it fails with 'This field can't contain spaces'.

Version-Release number of selected component (if applicable):
4.3
Worked on 4.2

How reproducible:
Easy

Steps to Reproduce:
1. Add or Edit a host
2. Select 'Kernel' 
3. Attempt set multiple kernel command line options e.g 'hugepagesz=1G hugepages=230'

Actual results:
Won't let you proceed. Field is red, mouse-over shows 'This field can't contain spaces'.

Expected results:
Can proceed. Command line options set for kernel.

Additional info:
This can also hinder if you already have multiple command line options set and have to edit the host for other reasons (cluster change, etc). It won't let you proceed unless you remove the additional options, but then you have no way to re-apply them through the gui.

Setting a single option without any spaces works fine.

I couldn't find any notes about a delimiter change for this field.
Comment 1 Ryan Barry 2019-02-10 00:10:46 UTC 
This is likely to be an effect of https://bugzilla.redhat.com/show_bug.cgi?id=1478854

The regular expression used is whitespace only, and shouldn't block "normal" whitespaces
Comment 2 Michael Burman 2019-03-07 10:10:13 UTC 
Verified on - rhvm-4.3.2-0.1.el7.noarch
Comment 3 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.