Foreman compute oVirt: New Host failing with action type cpu profile empty
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 -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767
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?
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). Doron [1] https://bugzilla.redhat.com/show_bug.cgi?id=1172207
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?
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
-- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767
On 29/06/15 10:51, Daniel Helgenberger wrote:
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?
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
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.
On 29.06.2015 09:56, Doron Fediuck wrote:
On 29/06/15 10:51, Daniel Helgenberger wrote:
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?
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
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. I knew about these issues and already have some other then the default cpu profiles. I just created a new template in ovirt witch does only use a diffrent cpu profile and used this template in Foreman; same error.
participants (2)
-
Daniel Helgenberger -
Doron Fediuck