Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 980879 - osinfo file - deriving properties from NON-existing section causes 'General command validation failure.' in UI
Summary: osinfo file - deriving properties from NON-existing section causes 'General c...
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.4.0
Assignee: Shahar Havivi
QA Contact: Pavel Novotny
Whiteboard: virt
Depends On:
Blocks: rhev3.4beta 1142926
TreeView+ depends on / blocked
Reported: 2013-07-03 12:25 UTC by Jiri Belka
Modified: 2014-09-18 12:24 UTC (History)
10 users (show)

Fixed In Version: ovirt-3.4.0-alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-06-12 14:06:28 UTC
oVirt Team: ---
Target Upstream Version:

Attachments (Terms of Use)
engine.log (deleted)
2013-07-03 12:25 UTC, Jiri Belka
no flags Details

System ID Priority Status Summary Last Updated
oVirt gerrit 19314 None None None Never

Description Jiri Belka 2013-07-03 12:25:15 UTC
Created attachment 768238 [details]

Description of problem:

when one defines a osinfo section deriving rest of property values from non-existent section, this "inconsistent" section is accepted and displayed in UI in 'Operating Systems'.

Selecting this operating system type for new VM causes following error in UI.

Error while executing action:


    General command validation failure.

I would say if a section is deriving property data from another section which do not exist, it should be ignored completely.

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

How reproducible:

Steps to Reproduce:
cat > $ENGINE_ETC/conf/osinfo.conf.d/ << _EOF = 999 = OpenIndiana = e1000
os.OpenIndiana.derivedFrom.value = Foobar
2. restart engine
3. create new VM while selecting OpenIndiana as Operating System in VM properties

Actual results:
error, "inconsistent" osinfo section is accepted

Expected results:
ignore "inconsistent" osinfo section

Additional info:

start checking log file since following line

2013-07-03 12:16:48,038 INFO  [org.ovirt.engine.core.utils.osinfo.OsInfoPreferencesLoader] (ServerService Thread Pool -- 38) Loaded file /etc/ovirt-engine/osinfo.conf.d/


Comment 1 Michal Skrivanek 2013-07-04 05:54:24 UTC
I think it should be either ignored completely or engine should fail to start

Comment 2 Jiri Belka 2013-08-12 10:03:04 UTC
Same issue with is9.1 with following scenario.

cat > /etc/ovirt-engine/osinfo.conf.d/ << _EOF = 666 = OpenBSD = pv
os.OpenBSD.derivedFrom.value = Other

New VM with OpenBSD 'Operating System' cannot be created:

General command validation failure.

Comment 3 Michal Skrivanek 2013-09-17 07:23:15 UTC
this is only in case user adds own config

Comment 4 Shahar Havivi 2013-09-17 08:45:44 UTC
patch sent at:

Comment 6 Jiri Belka 2013-12-04 14:28:58 UTC
in is25 error msg in UI is:

'Error while executing action New VM from Blank Template: Internal Engine Error' in UI.

Comment 7 Shahar Havivi 2013-12-05 12:35:30 UTC
(In reply to Jiri Belka from comment #6)
> in is25 error msg in UI is:
> 'Error while executing action New VM from Blank Template: Internal Engine
> Error' in UI.

Please provide more information,
Can you please provide the Engine log.

Comment 8 Sandro Bonazzola 2014-01-14 08:44:11 UTC
ovirt 3.4.0 alpha has been released

Comment 9 Pavel Novotny 2014-02-18 14:51:29 UTC
Verified upstream in ovirt-engine-3.4.0-0.7.beta2.el6.noarch.

Verification steps:
1. On oVirt Engine do:
cat > /etc/ovirt-engine/osinfo.conf.d/ << _EOF = 666 = OpenBSD = pv
os.OpenBSD.derivedFrom.value = Other
2. Restart ovirt-engine service.
3. Check engine.log file. Search for text "Loaded file /etc/ovirt-engine/osinfo.conf.d
4. In UI try to create VM with operating system "OpenBSD".

3. engine.log now says "Illegal parent for os: OpenBSD":
2014-02-18 15:34:06,675 INFO  [org.ovirt.engine.core.utils.osinfo.OsInfoPreferencesLoader] (MSC service thread 1-2) Loaded file /etc/ovirt-engine/osinfo.conf.d
2014-02-18 15:34:06,721 WARN  [org.ovirt.engine.core.utils.OsRepositoryImpl] (MSC service thread 1-2) Illegal parent for os: OpenBSD
4. No "OpenBSD" option is shown in Operating System select box.

Comment 11 Itamar Heim 2014-06-12 14:06:28 UTC
Closing as part of 3.4.0

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