Bug 1126774

The 7.0 guest image uses the key/description RHEL7x64 in the ova file, it looks like this key is unknown to RHEV-M:

$ egrep -rn RHEL.x64
frontend/webadmin/modules/uicompat/src/main/resources/org/ovirt/engine/ui/uicompat/Enums.properties:70:VmOsType___RHEL6x64=Red Hat Enterprise Linux 6.x x64
frontend/webadmin/modules/uicompat/src/main/resources/org/ovirt/engine/ui/uicompat/Enums.properties:72:VmOsType___RHEL5x64=Red Hat Enterprise Linux 5.x x64
frontend/webadmin/modules/uicompat/src/main/resources/org/ovirt/engine/ui/uicompat/Enums.properties:74:VmOsType___RHEL4x64=Red Hat Enterprise Linux 4.x x64
frontend/webadmin/modules/uicompat/src/main/resources/org/ovirt/engine/ui/uicompat/Enums.properties:76:VmOsType___RHEL3x64=Red Hat Enterprise Linux 3.x x64
packaging/conf/osinfo-defaults.properties:108:# RHEL4x64(14, OsType.Linux, true),
packaging/conf/osinfo-defaults.properties:354:backwardCompatibility.RHEL3x64 = 15
packaging/conf/osinfo-defaults.properties:356:backwardCompatibility.RHEL4x64 = 14
packaging/conf/osinfo-defaults.properties:358:backwardCompatibility.RHEL5x64 = 13
packaging/conf/osinfo-defaults.properties:360:backwardCompatibility.RHEL6x64 = 19
backend/manager/modules/bll/src/test/java/org/ovirt/engine/core/bll/HotPlugDiskToVmCommandTest.java:188:        when(osRepository.getOsName(15)).thenReturn("RHEL3x64");
$

This also has the affect that some things (i.e. setting the root password) do not work.

I'm raising the priority because if the user does not choose the correct operating system family manually, then setting the root password will fail.

Fabian,
RHEL 7 has been added in oVirt 3.4.1 bug 1083065 as
os.rhel_7x64.id.value = 24
os.rhel_7x64.name.value = Red Hat Enterprise Linux 7.x x64

What's missing?

Hey Michal, the RHEL guest images 7.0 OVA is using the description "RHEL7x64", that this did not translate to the correct description in RHEV-M.

Michal, can you tell if that "description" field in the OVA is used to determin the guest OS - or if a different field of the OVA is used?

Yu Liu, can you please provide the RHEV-M version you are using?

(In reply to Fabian Deutsch from comment #5)
> Michal, can you tell if that "description" field in the OVA is used to
> determin the guest OS - or if a different field of the OVA is used?

I was hoping it's the actual ID value…but I may be wrong
How does the OVA look like?

(In reply to Fabian Deutsch from comment #5)
> Hey Michal, the RHEL guest images 7.0 OVA is using the description
> "RHEL7x64", that this did not translate to the correct description in RHEV-M.
> 
> Michal, can you tell if that "description" field in the OVA is used to
> determin the guest OS - or if a different field of the OVA is used?
> 
> Yu Liu, can you please provide the RHEV-M version you are using?

Hi fabiand, I tried it on two version:
rhevm-setup-plugin-ovirt-engine-3.4.1-0.30.el6ev.noarch
rhevm-setup-plugin-ovirt-engine-3.4.0-0.16.rc.el6ev.noarch

Both using 3.4

the second one is 3.4.0 and as I said in comment #4 RHEL 7 was added in 3.4.1.

I also still need an answer to comment #6

Michal, what do you actualyl need from the OVA?

I don't know what's in the OVA you mentioned. Can you post the link or copy the relevant section? Does it have the ID there?

what's the original issue here anyway? https://bugzilla.redhat.com/show_bug.cgi?id=1111522#c0 ? It's not valid if the RHEV-M is 3.4.0 as RHEL 7 was *not* supported there, only since 3.4.1. Id and/or name need to match comment #4

Created attachment 928992 [details]
rhevm_other_os_problem

Created attachment 928993 [details]
rhevm_other_os_problem2

(In reply to Michal Skrivanek from comment #10)
> I don't know what's in the OVA you mentioned. Can you post the link or copy
> the relevant section? Does it have the ID there?
> 
> what's the original issue here anyway?
> https://bugzilla.redhat.com/show_bug.cgi?id=1111522#c0 ? It's not valid if
> the RHEV-M is 3.4.0 as RHEL 7 was *not* supported there, only since 3.4.1.
> Id and/or name need to match comment #4

I believe that the "OVA" what Fabiand said is acutally "OVF", it's located here after install rhel-guest-image rpm:
#pwd
/usr/share/rhel-guest-image-$x/$version/master/vms/$version

And the detail of describing operation system is below:

<Section ovf:id="f9350d95-31b7-41d4-87ac-1526fa1435ab" ovf:required="false" xsi:type="ovf:OperatingSystemSection_Type">
      <Info>Guest OS</Info>
      <Description>RHEL7x64</Description>
</Section>

By default, the Operating System supposed to be 'Red Hat Enterprise Linux 7.x x64' but in fact it's 'Other OS' instead.

Still confused if you're, please check these two pictures I attacked to the top.

(In reply to yuliu from comment #13)
great. thanks.
just to doublecheck…so you took this ovf and tried to import it into 3.4.1 environment and the bug still reproduces? Please confirm 3.4.1 vs 3.4.0

(In reply to Michal Skrivanek from comment #14)
> (In reply to yuliu from comment #13)
> great. thanks.
> just to doublecheck…so you took this ovf and tried to import it into 3.4.1
> environment and the bug still reproduces? Please confirm 3.4.1 vs 3.4.0

Yes, I can reproduce this bug in 3.4.1

engine expects to match the exact string (case sensitive) means: rhel_7x64 
if there is no match, "other" is used.

what generated this string?

(In reply to Omer Frenkel from comment #16)
> engine expects to match the exact string (case sensitive) means: rhel_7x64 
> if there is no match, "other" is used.
> 
> what generated this string?

A small script we use to create ovf.
So it's easy to change.

But I also plan to switch over to brews/kojis capabilities to build the ova, I'm not sure what brew is setting as a description.

What is confusing me a bit is, that the RHEL 6 images are using RHEL6x64, and we simply just changed the major version (so it becomes RHEL7x64).

I wonder why the RHEL6 images are identified correctly but not the RHEL 7 images.

I'm open to change the description string to match with the string in RHEVM

Right, this is the "old" os names (== before we introduced the OsInfo which is configuration on the guest os level) and it works because we need to keep backward compatibility.

if you look in share/ovirt-engine/conf/osinfo-defaults.properties
you can see the backward compatibility mapping for old naming

and new OS like rhel7 are not added there anymore.
so the right naming is rhel_Zx64 going fwd

Thanks for that informative answer. I will then adjust the description for the next update. That way the image should turn up correctly.

*** This bug has been marked as a duplicate of bug 1116122 ***