Bug 1654007

Summary: Allow updating kernel options on single-host install
Product: [oVirt] ovirt-node Reporter: Will Kline <will>
Component: Installation & UpdateAssignee: Yuval Turgeman <yturgema>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Lukas Svaty <lsvaty>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.2CC: bugs, cshao, michal.skrivanek, will
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-02-12 09:28:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of kernel parameters page none

Description Will Kline 2018-11-27 20:06:14 UTC
Created attachment 1509171 [details]
Screenshot of kernel parameters page

Description of problem:
After installing RHEV node 4.2 in single-node configuration, I setup the RHV vm, along with CFME and a few other VMs.  After doing this, I went to create a VM with a passthrough PCI device and found that I could not add it after setting up RHEV.

Version-Release number of selected component (if applicable):


How reproducible:
Very

Steps to Reproduce:
1. Install RHEV in single-host mode
2. Go to "compute" > "hosts" > select host > "kernel settings"
3.

Actual results:
"Kernel boot parameters changes require host deploy and restart. The host needs to be REINSTALLED suceesfully and then to be REBOOTED for kernel boot parameters to be applied!"

Expected results:
1. I should be able to reboot my single-host with changed configs.  There should be warnings, but not being able to ever reboot the host doesn't work.
2. UI should have prompted for this during the node installation,  or during the cockpit installation, then rebooted accordingly.
Additional info:

Comment 1 Michal Skrivanek 2018-11-28 12:20:47 UTC
It’s not too much hassle to do it afterwards, it’s just one more reboot. It would be nice to be able to select that on host deployment, but the amount of work is disproportional to the benefit. 

I do not understand that part about not being able to reboot. Is anything blocking that action?

Comment 2 Sandro Bonazzola 2019-02-12 09:28:40 UTC
Closing this bug with insufficient data pending needinfo since 2018-11-28.
If you can provide needed info feel free to reopen this bug.

Comment 3 Red Hat Bugzilla 2023-09-14 04:42:57 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days