[Users] Testing ovirt all in one on F18 gives error on DB creation
Alon Bar-Lev
alonbl at redhat.com
Thu Dec 6 17:03:20 UTC 2012
Thank you for testing!
----- Original Message -----
> From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com>
> To: "Itamar Heim" <iheim at redhat.com>
> Cc: "Juan Antonio Hernandez Fernandez" <jhernand at redhat.com>, "users" <users at ovirt.org>, "Ohad Basan"
> <obasan at redhat.com>
> Sent: Thursday, December 6, 2012 6:56:07 PM
> Subject: Re: [Users] Testing ovirt all in one on F18 gives error on DB creation
>
> In the mean time my tests on f18 with nightly build
> (ovirt-engine-3.2.0-1.20121204.git5d79c41.fc18.noarch) went ahead ...
>
<snip>
>
> 3) Installation failure probably caused by tuned-adm error
>
> under /var/log/ovirt-engine/host-deploy
>
> ovirt-20121205170118-f18aio.localdomain.local.log
>
> 2012-12-05 17:01:18 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned
> plugin.execute:393 execute-output: ('/sbin/tuned-adm', 'profile',
> 'vir
> tual-host') stderr:
> 2012-12-05 17:00:53,193 ERROR dbus.proxies: Introspect error on
> :1.43:/Tuned: dbus.exceptions.DBusException:
> org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
> causes include: the remote application did not send a reply, the
> message bus security policy blocked the reply, the reply timeout
> expired, or the network connection was broken.
> ERROR:dbus.proxies:Introspect error on :1.43:/Tuned:
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply:
> Did
> not receive a reply. Possible causes include: the remote application
> did not send a reply, the message bus security policy blocked the
> reply, the reply timeout expired, or the network connection was
> broken.
> DBus call to Tuned daemon failed (org.freedesktop.DBus.Error.NoReply:
> Did not receive a reply. Possible causes include: the remote
> application did not send a reply, the message bus security policy
> blocked the reply, the reply timeout expired, or the network
> connection was broken.).
>
> the same if I run from command line:
> /sbin/tuned-adm profile virtual-host
This must be a recent fedora issue, as I tested this recently on vanilla fedora 18 beta dvd and it worked properly.
As long as tuned-adm is not working properly when executed manually, the deployment automation will fail with same error.
Regards,
Alon
More information about the Users
mailing list