DescriptionAntoni Segura Puimedon
2014-10-24 17:43:27 UTC
Description of problem:
On a machine were I previously set up and uninstalled the hosted engine, I installed ovirt-hosted-engine-ha. It did not pull otopi and when trying to start it I got this backtrace:
Oct 24 19:38:36 dev-09.rhev.lab.eng.brq.redhat.com systemd-ovirt-ha-agent[7613]: from . import hosted_engine
Oct 24 19:38:36 dev-09.rhev.lab.eng.brq.redhat.com systemd-ovirt-ha-agent[7613]: File "/usr/lib/python2.7/site-pac...>
Oct 24 19:38:36 dev-09.rhev.lab.eng.brq.redhat.com systemd-ovirt-ha-agent[7613]: from ..lib import vds_client as vdsc
Oct 24 19:38:36 dev-09.rhev.lab.eng.brq.redhat.com systemd-ovirt-ha-agent[7613]: File "/usr/lib/python2.7/site-pac...>
Oct 24 19:38:36 dev-09.rhev.lab.eng.brq.redhat.com systemd-ovirt-ha-agent[7613]: from otopi import util
Oct 24 19:38:36 dev-09.rhev.lab.eng.brq.redhat.com systemd-ovirt-ha-agent[7613]: ImportError: No module named otopi
Oct 24 19:38:36 dev-09.rhev.lab.eng.brq.redhat.com systemd-ovirt-ha-agent[7613]: [FAILED]
Version-Release number of selected component (if applicable):
ovirt-hosted-engine-ha-1.2.4-1.fc20.noarch
How reproducible:
Steps to Reproduce:
1.install ovirt-hosted-engine-ha in a clean vdsm setup
2.systemctl start ovirt-ha-agent
Actual results:
The agent starts
Expected results:
the service fails to start with the aforementioned backtrace.
Additional info:
Comment 1Antoni Segura Puimedon
2014-10-24 17:44:06 UTC
Note that issuing yum install otopi fixes the problem.
Just a note, this will be resolved for completeness, but it's not
really a bug.
The right way to install hosted engine goes through hosted-engine-setup
which depends on:
Requires: otopi >= 1.3.0
....
Requires: ovirt-hosted-engine-ha >= 1.3.0
So this issue should not really happen if you install the setup
which is the only way to install hosted engine.