On 28.06.2015 14:40, Doron Fediuck wrote:
> On 26/06/15 12:21, Daniel Helgenberger wrote:
>> Hello,
>>
>> I have configured oVirt as compute resource in foreman. This is working
>> well to the point creating a new host, witch fails witch the error:
>>
>> 'Failed to create a compute oVirt (oVirt) instance wst01.int.m-box.de:
>> action type cpu profile empty'
>>
>> I found a (resolved but yet not closed) BZ1160846 [1] relating to disk
>> profiles.
>>
>> Versions:
>> foreman 1.8.1
>> ovirt engine 3.5.3
>>
>> Strangely I am unable to find anything in engine.log relating to the
>> attempt?
>>
>> [1]
https://bugzilla.redhat.com/show_bug.cgi?id=1160846
>>
> Hi Daniel,
> there are bugs reported for CPU profile, such as [1].
> If this is indeed the case (profile error) it should appear
> as an error in the engine.log (which may have rotated).
Hello Doron, right you are, I seem to have missed this when I first looked.
Reading the BZ I would rather say this is a Foreman issue and not ovirt
since rejecting the command is intended?
>
> Doron
>
> [1]
https://bugzilla.redhat.com/show_bug.cgi?id=1172207
>
Hi Daniel,
going forward we will have a default profile which will prevent such issues.
So for now I'd advise you simply to create a profile if needed as a workaround.