
This is a multi-part message in MIME format. --------------010107080600070007040200 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi folks, I'm new to the project, so please pardon my ignorance. I came to oVirt by way of looking for a suitable KVM/libvirt-based IaaS stack to supersede my old Ubuntu 12.04 setup, that I've been running since KVM came to Ubuntu-town. I've looked & tried a number of solutions - Eucalyptus, Enomalism, OpenStack - but most proved too cumbersome or admin-heavy for us. A while back I set up oVirt on CentOS (whatever was stable at the time), but had to shelve the project for a while, because... reasons. Fired it back up again & did all the requisite updates/upgrades to bring the host up to snuff. Unfortunately oVirt did not work as well, so I tried removing/purging it from the host & reinstalling it - both the 3.4.* stable & 3.5 beta - but both get hit up by the same issue when running the engine-setup. Details follow - Environment: Linux $REDACTED 2.6.32-431.20.5.el6.centos.plus.x86_64 #1 SMP Fri Jul 25 07:10:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux CentOS release 6.5 (Final) terminal-out: [ INFO ] Starting engine service [ ERROR ] Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140727140628-g0z922.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140727141521-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed log portion corresponding to the above error: 2014-07-27 13:25:01 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py", line 51, in _closeup state=True, File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 188, in state 'start' if state else 'stop' File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 96, in _executeServiceCommand raiseOnError=raiseOnError File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 871, in execute command=args[0], RuntimeError: Command '/sbin/service' failed to execute 2014-07-27 13:25:01 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute & 2014-07-27 17:40:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:866 execute-output: ('/sbin/service', 'ovirt-engine', 'start') stderr: 2014-07-27 17:40:58 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py", line 57, in _closeup state=True, File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 188, in state 'start' if state else 'stop' File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 96, in _executeServiceCommand raiseOnError=raiseOnError File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 871, in execute command=args[0], RuntimeError: Command '/sbin/service' failed to execute 2014-07-27 17:40:58 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:468 ENVIRONMENT DUMP - BEGIN 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'True' 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError("Command '/sbin/service' failed to execute",), <traceback object at 0x27fdf80>)]' 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:482 ENVIRONMENT DUMP - END 2014-07-27 17:40:58 INFO otopi.context context.runSequence:395 Stage: Clean up 2014-07-27 17:40:58 DEBUG otopi.context context.runSequence:399 STAGE cleanup 2014-07-27 17:40:58 DEBUG otopi.context context._executeMethod:138 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.core.misc.Plugin._cleanup I've had a dig around & from what I can tell this (possibly) related to bugs that would've been patched in the stable release (& beta?) that I've installed, but the issue persists. I'm not certain where the issue could be coming in (lower-level/OS dependency maybe?), or if I've missed something. I've flushed & reloaded the full stack already, with the same outcome. Next I'll have to wipe the OS & start again, with no guarantee this issue won't reoccur. My next step would simply be to try out the oVirt live image. Does the image provide an option to install to the host? (looking at the live node installers, it seems likely) Are these images *purely* for PoC/demo/testing (i.e. highly unstable), or would it be stable enough for in-house (Docker) prototyping before deploying to a hosted/stable/production environment? Cheers - Jaco --------------010107080600070007040200 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi folks,<br> <br> I'm new to the project, so please pardon my ignorance.<br> <br> I came to oVirt by way of looking for a suitable KVM/libvirt-based IaaS stack to supersede my old Ubuntu 12.04 setup, that I've been running since KVM came to Ubuntu-town.<br> <br> I've looked & tried a number of solutions - Eucalyptus, Enomalism, OpenStack - but most proved too cumbersome or admin-heavy for us.<br> <br> A while back I set up oVirt on CentOS (whatever was stable at the time), but had to shelve the project for a while, because... reasons. Fired it back up again & did all the requisite updates/upgrades to bring the host up to snuff.<br> <br> Unfortunately oVirt did not work as well, so I tried removing/purging it from the host & reinstalling it - both the 3.4.* stable & 3.5 beta - but both get hit up by the same issue when running the engine-setup.<br> <br> Details follow -<br> <br> Environment:<br> <br> Linux $REDACTED 2.6.32-431.20.5.el6.centos.plus.x86_64 #1 SMP Fri Jul 25 07:10:09<br> UTC 2014 x86_64 x86_64 x86_64 GNU/Linux <meta http-equiv="content-type" content="text/html; charset=utf-8"> <br> <br> CentOS release 6.5 (Final) <meta http-equiv="content-type" content="text/html; charset=utf-8"> <br> <br> terminal-out:<br> [ INFO ] Starting engine service <br> [ ERROR ] Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute <br> [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140727140628-g0z922.log <br> [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140727141521-setup.conf' <br> [ INFO ] Stage: Pre-termination <br> [ INFO ] Stage: Termination <br> [ ERROR ] Execution of setup failed<br> <br> log portion corresponding to the above error:<br> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <pre class="bz_comment_text bz_wrap_comment_text" id="comment_text_11" style="font-size: small; font-family: monospace; white-space: pre-wrap; word-wrap: break-word; width: 50em; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">2014-07-27 13:25:01 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py", line 51, in _closeup state=True, File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 188, in state 'start' if state else 'stop' File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 96, in _executeServiceCommand raiseOnError=raiseOnError File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 871, in execute command=args[0], RuntimeError: Command '/sbin/service' failed to execute 2014-07-27 13:25:01 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute</pre> <br> &<br> <br> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <pre class="bz_comment_text bz_wrap_comment_text" id="comment_text_12" style="font-size: small; font-family: monospace; white-space: pre-wrap; word-wrap: break-word; width: 50em; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">2014-07-27 17:40:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:866 execute-output: ('/sbin/service', 'ovirt-engine', 'start') stderr: 2014-07-27 17:40:58 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py", line 57, in _closeup state=True, File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 188, in state 'start' if state else 'stop' File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 96, in _executeServiceCommand raiseOnError=raiseOnError File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 871, in execute command=args[0], RuntimeError: Command '/sbin/service' failed to execute 2014-07-27 17:40:58 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:468 ENVIRONMENT DUMP - BEGIN 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'True' 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError("Command '/sbin/service' failed to execute",), <traceback object at 0x27fdf80>)]' 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:482 ENVIRONMENT DUMP - END 2014-07-27 17:40:58 INFO otopi.context context.runSequence:395 Stage: Clean up 2014-07-27 17:40:58 DEBUG otopi.context context.runSequence:399 STAGE cleanup 2014-07-27 17:40:58 DEBUG otopi.context context._executeMethod:138 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.core.misc.Plugin._cleanup</pre> <br> I've had a dig around & from what I can tell this (possibly) related to bugs that would've been patched in the stable release (& beta?) that I've installed, but the issue persists.<br> <br> I'm not certain where the issue could be coming in (lower-level/OS dependency maybe?), or if I've missed something. <br> I've flushed & reloaded the full stack already, with the same outcome. Next I'll have to wipe the OS & start again, with no guarantee this issue won't reoccur.<br> <br> My next step would simply be to try out the oVirt live image.<br> Does the image provide an option to install to the host? (looking at the live node installers, it seems likely)<br> <br> Are these images *purely* for PoC/demo/testing (i.e. highly unstable), or would it be stable enough for in-house (Docker) prototyping before deploying to a hosted/stable/production environment?<br> <br> Cheers<br> <br> - Jaco<br> </body> </html> --------------010107080600070007040200--

----- Original Message -----
From: "Jaco" <bakgatnet@gmail.com> To: Users@ovirt.org Sent: Tuesday, July 29, 2014 5:22:44 AM Subject: [ovirt-users] Setting up all-in-one
Hi folks,
I'm new to the project, so please pardon my ignorance.
I came to oVirt by way of looking for a suitable KVM/libvirt-based IaaS stack to supersede my old Ubuntu 12.04 setup, that I've been running since KVM came to Ubuntu-town.
I've looked & tried a number of solutions - Eucalyptus, Enomalism, OpenStack - but most proved too cumbersome or admin-heavy for us.
Well, hopefully you'll find oVirt best :-)
A while back I set up oVirt on CentOS (whatever was stable at the time), but had to shelve the project for a while, because... reasons. Fired it back up again & did all the requisite updates/upgrades to bring the host up to snuff.
Unfortunately oVirt did not work as well, so I tried removing/purging it from the host & reinstalling it - both the 3.4.* stable & 3.5 beta - but both get hit up by the same issue when running the engine-setup.
Details follow -
Environment:
Linux $REDACTED 2.6.32-431.20.5.el6.centos.plus.x86_64 #1 SMP Fri Jul 25 07:10:09 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
CentOS release 6.5 (Final)
terminal-out: [ INFO ] Starting engine service [ ERROR ] Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute [ INFO ] Stage: Clean up Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20140727140628-g0z922.log [ INFO ] Generating answer file '/var/lib/ovirt-engine/setup/answers/20140727141521-setup.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Execution of setup failed
log portion corresponding to the above error: 2014-07-27 13:25:01 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py", line 51, in _closeup state=True, File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 188, in state 'start' if state else 'stop' File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 96, in _executeServiceCommand raiseOnError=raiseOnError File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 871, in execute command=args[0], RuntimeError: Command '/sbin/service' failed to execute 2014-07-27 13:25:01 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute
&
2014-07-27 17:40:58 DEBUG otopi.plugins.otopi.services.rhel plugin.execute:866 execute-output: ('/sbin/service', 'ovirt-engine', 'start') stderr:
2014-07-27 17:40:58 DEBUG otopi.context context._executeMethod:152 method exception Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/otopi/context.py", line 142, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/system/engine.py", line 57, in _closeup state=True, File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 188, in state 'start' if state else 'stop' File "/usr/share/otopi/plugins/otopi/services/rhel.py", line 96, in _executeServiceCommand raiseOnError=raiseOnError File "/usr/lib/python2.6/site-packages/otopi/plugin.py", line 871, in execute command=args[0], RuntimeError: Command '/sbin/service' failed to execute
2014-07-27 17:40:58 ERROR otopi.context context._executeMethod:161 Failed to execute stage 'Closing up': Command '/sbin/service' failed to execute 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:468 ENVIRONMENT DUMP - BEGIN 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/error=bool:'True' 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:478 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError("Command '/sbin/service' failed to execute",), <traceback object at 0x27fdf80>)]' 2014-07-27 17:40:58 DEBUG otopi.context context.dumpEnvironment:482 ENVIRONMENT DUMP - END 2014-07-27 17:40:58 INFO otopi.context context.runSequence:395 Stage: Clean up 2014-07-27 17:40:58 DEBUG otopi.context context.runSequence:399 STAGE cleanup 2014-07-27 17:40:58 DEBUG otopi.context context._executeMethod:138 Stage cleanup METHOD otopi.plugins.ovirt_engine_common.base.core.misc.Plugin._cleanup
These snippets are not enough to see *which* service failed to start - you should look a few lines before that. If it's the engine itself, you should look at its logs (/var/log/ovirt-engine/*.log). If it's vdsm, its own (/var/log/vdsm), etc. So please post relevant portions from the logs of the failing service.
I've had a dig around & from what I can tell this (possibly) related to bugs that would've been patched in the stable release (& beta?) that I've installed, but the issue persists.
I'm not certain where the issue could be coming in (lower-level/OS dependency maybe?), or if I've missed something. I've flushed & reloaded the full stack already, with the same outcome.
Did this include removing and reinstalling vdsm/libvirt? If not, you might want to try that before reinstalling the OS.
Next I'll have to wipe the OS & start again, with no guarantee this issue won't reoccur.
If the host wasn't used for anything else, this is probably simplest.
My next step would simply be to try out the oVirt live image. Does the image provide an option to install to the host? (looking at the live node installers, it seems likely)
IIRC it does not.
Are these images *purely* for PoC/demo/testing (i.e. highly unstable), or would it be stable enough for in-house (Docker) prototyping before deploying to a hosted/stable/production environment?
They are Poc/Demo only. I wouldn't say "highly unstable", but prototyping wasn't a design consideration. Basically these images are very similar to what you'll get when installing a clean OS with all-in-one, with a few differences intended to automate everything, so that the user will not have to answer anything. Note that engine-setup is ran by it after boot, the engine is not pre-setup in the image. Best, -- Didi

Cheers & thanks for the reply. On 29/07/14 17:52, Yedidyah Bar David wrote:
Well, hopefully you'll find oVirt best :-) cheers :)
These snippets are not enough to see *which* service failed to start - you should look a few lines before that. I searched for the [ERROR] bit & looked around that, but I'll take another look, thanks If it's the engine itself, you should look at its logs (/var/log/ovirt-engine/*.log). If it's vdsm, its own (/var/log/vdsm), etc. Oh, gosh! Now it's coming back to me re the interconnected bits & where they failed the last time 'round
Did this include removing and reinstalling vdsm/libvirt? If not, you might want to try that before reinstalling the OS. Yea - I did. I noticed in the log it ref's Python 2.6, where 2.7 is much more current, making me question if it's something underlying.
They are Poc/Demo only. I wouldn't say "highly unstable", but prototyping wasn't a design consideration. Basically these images are very similar to what you'll get when installing a clean OS with all-in-one, with a few differences intended to automate everything, so that the user will not have to answer anything. Note that engine-setup is ran by it after boot, the engine is not pre-setup in the image. Think I'll try a live USB instance to see what the system is capable of & a semi-stable setup should look like & wipe & redo the host if the issue persists.
Thanks for the help & kind word. I'll report back.... Cheers - J
participants (2)
-
Jaco
-
Yedidyah Bar David