Description of problem: The reported Host OS value by the engine failed parsing by the host-resource, therefore only the 'full_version' of the Host OS is being reported. Version-Release number of selected component (if applicable): master How reproducible: Always Steps to Reproduce: 1. Send GET request to 2. Examine the <os> element in the response. Actual results: The reported Host OS element looks like: <os type="RHEL"> <version full_version="7.2 - 9.el7"/> </os> Expected results: The <os><version></version></os> should include the version parts: <major/><minor/><release/><build/> Additional info: Here are several formats of the reported Host OS to be parsed: for rhel: RHEL - 7.2 - 9.el7 RHEL - 7 - 1.1503.el7.centos.2.8 ovirt-node: oVirt Node - 3.6 - 0.999.201608161021.el7.centos for RHEV-H: RHEV Hypervisor - 7.2 - 20160711.0.el7ev
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
I get this [1] output from API but there isn't <release/> tag as mentioned in description, is it okay? [1] <os> <custom_kernel_cmdline/> <reported_kernel_cmdline>BOOT_IMAGE=/vmlinuz-3.10.0-327.22.2.el7.x86_64 root=/dev/mapper/rootvg-lv_root ro consoleblank=0 crashkernel=auto rd.lvm.lv=rootvg/lv_root rd.lvm.lv=rootvg/lv_swap rhgb quiet LANG=en_US.UTF-8 </reported_kernel_cmdline> <type>RHEL</type> <version> <full_version>7.2 - 9.el7</full_version> <major>7</major> <minor>2</minor> </version> </os>
Only major and minor are shown in API, if user wants to check release, he had to use full_version, because there is no consistent/unified way how to parse/report release, because release is specific for each OS.
Verified in ovirt-engine-restapi-4.0.4.1-0.1.el7ev.noarch