[Users] Testing ovirt all in one on F18 gives error on DB creation

Gianluca Cecchi gianluca.cecchi at gmail.com
Thu Dec 6 11:56:07 EST 2012


In the mean time my tests on f18 with nightly build
(ovirt-engine-3.2.0-1.20121204.git5d79c41.fc18.noarch) went ahead ...

PREFACE: this is a f18 vm in a fedora 17 host, where I put this in xml

  <cpu mode='custom' match='exact'>
    <model fallback='allow'>SandyBridge</model>
    <vendor>Intel</vendor>
    <feature policy='require' name='osxsave'/>
    <feature policy='require' name='pdcm'/>
    <feature policy='require' name='xtpr'/>
    <feature policy='require' name='tm2'/>
    <feature policy='require' name='est'/>
    <feature policy='require' name='smx'/>
    <feature policy='require' name='vmx'/>
    <feature policy='require' name='ds_cpl'/>
    <feature policy='require' name='monitor'/>
    <feature policy='require' name='dtes64'/>
    <feature policy='require' name='pbe'/>
    <feature policy='require' name='tm'/>
    <feature policy='require' name='ht'/>
    <feature policy='require' name='ss'/>
    <feature policy='require' name='acpi'/>
    <feature policy='require' name='ds'/>
    <feature policy='require' name='vme'/>
    <feature policy='disable' name='aes'/>
  </cpu>

It goes through in installation, but now it fails at instaling the host

Creating Database...                                               [ DONE ]
Updating the Default Data Center Storage Type...                   [ DONE ]
Editing oVirt Engine Configuration...                              [ DONE ]
Editing Postgresql Configuration...                                [ DONE ]
Configuring the Default ISO Domain...                              [ DONE ]
Configuring Firewall (iptables)...                                 [ DONE ]
Starting ovirt-engine Service...                                   [ DONE ]
Configuring HTTPD...                                               [ DONE ]
AIO: Creating storage directory...                                 [ DONE ]
AIO: Adding Local Datacenter and cluster...                        [ DONE ]
AIO: Adding Local host (This may take several minutes)...       [ ERROR ]
Error: Timed out while waiting for host to start
Please check log file
/var/log/ovirt-engine/engine-setup_2012_12_05_16_57_11.log for more
information

NOTE: In log file I found:

1) problem with loading files to iso domain
2012-12-05 16:59:51::ERROR::engine-setup::1694::root:: Traceback (most
recent call last):
  File "/usr/bin/engine-setup", line 1691, in _loadFilesToIsoDomain
    utils.copyFile(filename, targetPath, basedefs.CONST_VDSM_UID,
basedefs.CONST_KVM_GID)
  File "/usr/share/ovirt-engine/scripts/common_utils.py", line 653, in copyFile
    shutil.copy2(fileSrc, destination)
  File "/usr/lib64/python2.7/shutil.py", line 128, in copy2
    copyfile(src, dst)
  File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile
    with open(src, 'rb') as fsrc:
IOError: [Errno 2] No such file or directory:
'/usr/share/virtio-win/virtio-win.vfd'

2012-12-05 16:59:51::ERROR::engine-setup::1695::root:: Failed to copy
files to iso domain

---> probably to include some deendency when you install packages?

2) Install of host fails

2012-12-05 17:00:24::DEBUG::all_in_one_100::279::root:: current host
status is: installing
2012-12-05 17:00:24::DEBUG::all_in_one_100::290::root:: Traceback
(most recent call last):
  File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py",
line 287, in isHostUp
    raise Exception(INFO_CREATE_HOST_WAITING_UP)
Exception: Waiting for the host to start

2012-12-05 17:00:29::DEBUG::all_in_one_100::276::root:: Waiting for
host to become operational
2012-12-05 17:00:29::DEBUG::all_in_one_100::279::root:: current host
status is: installing
2012-12-05 17:00:29::DEBUG::all_in_one_100::290::root:: Traceback
(most recent call last):
  File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py",
line 287, in isHostUp
    raise Exception(INFO_CREATE_HOST_WAITING_UP)
Exception: Waiting for the host to start

2012-12-05 17:01:15::DEBUG::all_in_one_100::276::root:: Waiting for
host to become operational
2012-12-05 17:01:15::DEBUG::all_in_one_100::279::root:: current host
status is: installing
2012-12-05 17:01:15::DEBUG::all_in_one_100::290::root:: Traceback
(most recent call last):
  File "/usr/share/ovirt-engine/scripts/plugins/all_in_one_100.py",
line 287, in isHostUp
    raise Exception(INFO_CREATE_HOST_WAITING_UP)
Exception: Waiting for the host to start

2012-12-05 17:01:20::DEBUG::all_in_one_100::276::root:: Waiting for
host to become operational
2012-12-05 17:01:20::DEBUG::all_in_one_100::279::root:: current host
status is: install_failed
2012-12-05 17:01:20::DEBUG::all_in_one_100::290::root:: Traceback
(most recent call last):

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


NOTE: in messages I have
2012-12-05 17:00:53,207 INFO     tuned.profiles.loader: loading
profile: virtual-host
2012-12-05 17:00:53,212 INFO     tuned.daemon.daemon: starting tuning
2012-12-05 17:00:53,220 INFO     tuned.units.manager: creating unit
'sysctl' (devices: sysctl)
2012-12-05 17:00:53,243 INFO     tuned.units.manager: skipping unit
'mounts', no devices available
2012-12-05 17:00:53,244 INFO     tuned.units.manager: skipping unit
'disk', no devices available
2012-12-05 17:00:53,246 INFO     tuned.units.manager: creating unit
'vm' (devices: vm)
2012-12-05 17:00:53,246 INFO     tuned.units.manager: creating unit
'cpu' (devices: 0)
2012-12-05 17:00:53,289 ERROR    tuned.utils.commands: Executing cpupower error:
2012-12-05 17:00:53,289 INFO     tuned.plugins.plugin_cpu: setting
governor 'performance' on cpu '0'
2012-12-05 17:00:53,300 ERROR    tuned.utils.commands: Executing cpupower error:
2012-12-05 17:01:03,301 INFO     tuned.plugins.plugin_cpu: new cpu latency 100

--> Possibly tuned-adm not supported in a guest? Skippable?

4)  I can open the weadmin portal and see the local_cluser configuration
Trying to re-install the host from web interface gives the same error

In messages during install of host I find this:

Dec  6 17:04:07 f18aio setroubleshoot: SELinux is preventing
/usr/bin/lsblk from search access on the directory udev. For complete
SELinux
messages. run sealert -l 5f88c680-1876-4bd5-b800-767cba201f73

don't know if it can be related, but I noticed that in output of
"sealert -l" it says to run audit2allow to create policy:

"
If you believe that lsblk should be allowed search access on the udev
directory by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep lsblk /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
"

and audit2allow was not present on my system.
In f17 it is in policycoreutils-python (that I have in my f18 too)
In f18 it is instead in policycoreutils-devel
So in case the audit2allow command could be of any importance during
installation of oVirt, policycoreutils-devel has to be a dependency.

Gianluca



More information about the Users mailing list