Bug 1320059 - vdsm _reconfigure should be called before _start
Summary: vdsm _reconfigure should be called before _start
Alias: None
Product: ovirt-host-deploy
Classification: oVirt
Component: Plugins.VDSM
Version: master
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-alpha
: 1.5.0
Assignee: Sandro Bonazzola
QA Contact: Petr Kubica
Depends On:
TreeView+ depends on / blocked
Reported: 2016-03-22 09:02 UTC by Dan Kenigsberg
Modified: 2016-07-27 13:04 UTC (History)
4 users (show)

Fixed In Version: ovirt 4.0.0 alpha1
Doc Type: Bug Fix
Doc Text:
Cause: a missing prioritization of the plugins which configure the host on host deployment allowed vdsm to start prior of being configured. Consequence: ugly errors in the log and slow down of the deployment process Fix: prioritized the configuration of vdsm to be done before vdsm starting Result: vdsm is configured when starting so the deploy is slightly faster and doesn't log ugly errors.
Clone Of:
Last Closed: 2016-07-27 13:04:53 UTC
oVirt Team: Integration
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 55183 0 master MERGED vdsm: give vdsm config higher priority 2016-03-24 10:49:10 UTC

Description Dan Kenigsberg 2016-03-22 09:02:59 UTC
Description of problem:
ykaul showed me a /var/log/messages that shows that vdsm is started by o-h-d prior of being configured. This causes ugly errors in the log, and slows down the deployment process.

Version-Release number of selected component (if applicable):
probably in current master 857e52dfd9ddcb772fddb4

How reproducible:
at least once

Steps to Reproduce:
1. as a host to an ovirt cluster within Lago

Actual results:
/var/log/messages of added host shows vdsm failing to start several times, followed by a `vdsm-tool configure` call, and a successful start.

Expected results:
install vdsm, configure it, and only then - start it.

Comment 1 Gil Klein 2016-07-27 13:04:53 UTC
This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA

Note You need to log in before you can comment on or make changes to this bug.