Bug 1320059

Summary: vdsm _reconfigure should be called before _start
Product: [oVirt] ovirt-host-deploy Reporter: Dan Kenigsberg <danken>
Component: Plugins.VDSMAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kubica <pkubica>
Severity: medium Docs Contact:
Priority: high    
Version: masterCC: bugs, danken, gklein, oourfali
Target Milestone: ovirt-4.0.0-alphaFlags: rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+
Target Release: 1.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 13:04:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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