<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Hi,</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">

Dropping VDSM list because I&#39;m not subscribed.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Using the nightly repo it seems to be fixed. I will continue to report any new findings.</div>

<div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Thanks,</div><div class="gmail_default" style="font-family:tahoma,sans-serif">Andrew.</div>

<div class="gmail_extra">
<br><br><div class="gmail_quote">On Tue, Jan 14, 2014 at 8:52 PM, Sandro Bonazzola <span dir="ltr">&lt;<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Il 14/01/2014 03:39, Andrew Lau ha scritto:<br>
<div class="im">&gt; It looks like vdsm is trying to execute:<br>
&gt; vdsm-tool unified_network_persistence_upgrade<br>
&gt;<br>
&gt; But my version of vdsm-tool has it labeled as &quot;upgrade-unified-persistence&quot;<br>
<br>
</div>vdsm people, can you check this?<br>
<div><div class="h5"><br>
<br>
<br>
&gt;<br>
&gt; On Tue, Jan 14, 2014 at 1:32 PM, Andrew Lau &lt;<a href="mailto:andrew@andrewklau.com">andrew@andrewklau.com</a> &lt;mailto:<a href="mailto:andrew@andrewklau.com">andrew@andrewklau.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt;     Hi,<br>
&gt;<br>
&gt;     I&#39;m giving the new hosted-engine feature a try with the new 3.4.0 alpha build on centos 6.5<br>
&gt;<br>
&gt;     hosted-engine --deply seems to fail at the &#39;Environment setup&quot;<br>
&gt;     [ ERROR ] Failed to execute stage &#39;Environment setup&#39;: Command &#39;/sbin/service&#39; failed to execute<br>
&gt;<br>
&gt;     Within the logs I believe it seems to be related to vdsm. Logs show  &quot;VDS daemon is not running&quot;<br>
&gt;<br>
&gt;     service vdsm start gives the following error:<br>
&gt;<br>
&gt;     initctl: Job is already running: libvirtd<br>
&gt;     vdsm: Running mkdirs<br>
&gt;     vdsm: Running configure_coredump<br>
&gt;     vdsm: Running run_init_hooks<br>
&gt;     vdsm: Running gencerts<br>
&gt;     vdsm: Running check_is_configured<br>
&gt;     libvirt is already configured for vdsm<br>
&gt;     sanlock service is already configured<br>
&gt;     vdsm: Running validate_configuration<br>
&gt;     SUCCESS: ssl configured to true. No conflicts<br>
&gt;     vdsm: Running prepare_transient_repository<br>
&gt;     vdsm: Running syslog_available<br>
&gt;     vdsm: Running nwfilter<br>
&gt;     vdsm: Running dummybr<br>
&gt;     vdsm: Running load_needed_modules<br>
&gt;     vdsm: Running tune_system<br>
&gt;     vdsm: Running test_space<br>
&gt;     vdsm: Running test_lo<br>
&gt;     vdsm: Running restore_nets<br>
&gt;     vdsm: Running unified_network_persistence_upgrade<br>
&gt;     Usage: /usr/bin/vdsm-tool [options] &lt;action&gt; [arguments]<br>
&gt;<br>
&gt;     Valid options:<br>
&gt;       -h, --help<br>
&gt;<br>
&gt;     Commands in module configurator:<br>
&gt;       configure                Configure external services for vdsm<br>
&gt;       is-configured            Determine if module is configured<br>
&gt;       validate-config          Determine if configuration is valid<br>
&gt;<br>
&gt;     Commands in module dummybr:<br>
&gt;       dummybr                  Defines dummy bridge on libvirt network.<br>
&gt;<br>
&gt;     Commands in module load_needed_modules:<br>
&gt;       load-needed-modules      Load needed modules<br>
&gt;<br>
&gt;     Commands in module nwfilter:<br>
&gt;       nwfilter                 Defines network filters on libvirt<br>
&gt;<br>
&gt;     Commands in module passwd:<br>
&gt;       set-saslpasswd           Set vdsm password for libvirt connection<br>
&gt;<br>
&gt;     Commands in module restore_nets:<br>
&gt;       restore-nets             Restores the networks to what was<br>
&gt;                           previously persisted via vdsm.<br>
&gt;<br>
&gt;     Commands in module seboolsetup:<br>
&gt;       sebool-config       Enable the required selinux booleans<br>
&gt;       sebool-unconfig     Disable the required selinux booleans<br>
&gt;<br>
&gt;     Commands in module service:<br>
&gt;       service-disable          Disable a system service<br>
&gt;       service-is-managed       Check the existence of a service<br>
&gt;       service-reload           Notify a system service to reload<br>
&gt;                           configurations<br>
&gt;       service-restart          Restart a system service<br>
&gt;       service-start            Start a system service<br>
&gt;       service-status           Get status of a system service<br>
&gt;       service-stop             Stop a system service<br>
&gt;<br>
&gt;     Commands in module transient:<br>
&gt;       cleanup-transient-repository     Cleanup the unused transient disks<br>
&gt;                                   present in the repository.     (NOTE: it<br>
&gt;                                   is recommended to NOT execute this<br>
&gt;                                   command when the vdsm     daemon is<br>
&gt;                                   running)<br>
&gt;       setup-transient-repository     Prepare the transient disks<br>
&gt;                                 repository<br>
&gt;<br>
&gt;     Commands in module unified_persistence:<br>
&gt;       upgrade-unified-persistence     Upgrade host networking persistence<br>
&gt;                                  from ifcfg to unified if the<br>
&gt;                                  persistence model is set as unified in<br>
&gt;                                  /usr/lib64/python2.X/site-packages/<br>
&gt;                                  vdsm/config.py<br>
&gt;<br>
&gt;     Commands in module upgrade:<br>
&gt;<br>
&gt;     Commands in module upgrade_300_networks:<br>
&gt;       upgrade-3.0.0-networks     Since ovirt-3.0, Vdsm uses libvirt<br>
&gt;                             networks (with names vdsm-*) to store     its<br>
&gt;                             own networks. Older Vdsms did not have those<br>
&gt;                             defined, and used only     linux bridges. This<br>
&gt;                             command is kept as an upgrade tool for the<br>
&gt;                             (very few)     people who still have such old<br>
&gt;                             setups running.<br>
&gt;<br>
&gt;     Commands in module validate_ovirt_certs:<br>
&gt;       validate-ovirt-certs     Validate vdsmcert.pem against cacert.pem.<br>
&gt;                           If current cacert.pem is invalidate, it will<br>
&gt;                           find a validate certificate     file and replace<br>
&gt;                           the old cacert.pem with it. And then persist it.<br>
&gt;<br>
&gt;     Commands in module vdsm-id:<br>
&gt;       vdsm-id                  Printing host uuid<br>
&gt;<br>
&gt;     vdsm: failed to execute unified_network_persistence_upgrade, error code 1<br>
&gt;     vdsm start                                                 [FAILED]<br>
&gt;<br>
&gt;     Any suggestions?<br>
&gt;<br>
&gt;     Thanks,<br>
&gt;     Andrew<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div>&gt; _______________________________________________<br>
&gt; Users mailing list<br>
&gt; <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
&gt; <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
&gt;<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Sandro Bonazzola<br>
Better technology. Faster innovation. Powered by community collaboration.<br>
See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br>
</font></span></blockquote></div><br></div></div>