Bug 1341268 - REST API for Kernel cmdline
Summary: REST API for Kernel cmdline
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.1
: 4.0.0
Assignee: jniederm
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On: 1301104
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-31 15:47 UTC by jniederm
Modified: 2016-08-12 14:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-12 14:11:38 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.0.z+
rule-engine: planning_ack+
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 58377 0 master MERGED Host kernel cmdline API 2016-06-24 09:31:43 UTC
oVirt gerrit 58391 0 master MERGED restapi: Host kernel cmdline 2016-06-24 14:12:49 UTC
oVirt gerrit 58700 0 master ABANDONED restapi: VM and Host OperatingSystem separated 2016-06-23 18:00:29 UTC
oVirt gerrit 58701 0 master ABANDONED OperatingSystem split to Host and VM one 2016-06-23 17:59:56 UTC
oVirt gerrit 59732 0 model_4.0 MERGED Host kernel cmdline API 2016-06-24 09:49:09 UTC
oVirt gerrit 59752 0 ovirt-engine-4.0 MERGED restapi: Host kernel cmdline 2016-06-27 10:18:40 UTC

Description jniederm 2016-05-31 15:47:25 UTC
Description of problem:
REST API for Kernel cmdline

Comment 1 Red Hat Bugzilla Rules Engine 2016-05-31 15:47:34 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 2 Israel Pinto 2016-08-10 08:09:14 UTC
Verify with:
Engine: 4.0.2.4-0.1.el7ev
Host: 
OS Version:RHEL - 7.2 - 9.el7_2.1
Kernel Version:3.10.0 - 327.22.2.el7.x86_64
KVM Version:2.3.0 - 31.el7_2.21
LIBVIRT Version:libvirt-1.2.17-13.el7_2.5
VDSM Version:vdsm-4.18.5.1-1.el7ev

Steps: 
Check custom parameter 'custom_kernel_cmdline': 
1. Update via REST 
like: 
<os>
<custom_kernel_cmdline>intel_iommu=on kvm-intel.nested=1 vfio_iommu_type1.allow_unsafe_interrupts=1</custom_kernel_cmdline>
</os>
2. Check that parameter updated in REST and UI
3. Re-install host and check that parameter is pass to OS,
check in /var/log/ovirt-engine/host-deploy/<host_name_date>
like:
2016-08-10 10:42:27 DEBUG otopi.context context.dumpEnvironment:770 ENV KERNEL/cmdlineNew=str:'intel_iommu=on kvm-intel.nested=1 vfio_iommu_type1.allow_unsafe_interrupts=1'
--------------------------------------------------------
Check none custom parameter: reported_kernel_cmdline
1. Update reported_kernel_cmdline parameter and check that no error occur since
if read only parameter.
like 
<os>
<reported_kernel_cmdline>BOOT_IMAGE=/vmlinuz-3.10.0-327.22.2.el7.x86_64 root=/dev/mapper/vg0-lv_root ro rd.lvm.lv=vg0/lv_root crashkernel=auto rd.lvm.lv=vg0/lv_swap rhgb quiet LANG=en_US.UTF-8</reported_kernel_cmdline>
</os>

All checks PASS


Note You need to log in before you can comment on or make changes to this bug.