Bug 1490104
Summary: | vdsm-tool does not start required services before configuring the host | |||
---|---|---|---|---|
Product: | [oVirt] ovirt-provider-ovn | Reporter: | Mor <mkalfon> | |
Component: | driver | Assignee: | Marcin Mirecki <mmirecki> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mor <mkalfon> | |
Severity: | medium | Docs Contact: | ||
Priority: | high | |||
Version: | 1.0.4 | CC: | bugs, danken, mkalfon, ylavi | |
Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
|
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | No Doc Update | ||
Doc Text: |
undefined
|
Story Points: | --- | |
Clone Of: | ||||
: | 1491546 (view as bug list) | Environment: | ||
Last Closed: | 2017-12-20 11:01:40 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Mor
2017-09-10 10:50:53 UTC
We may want to use `ovs-vsctl --no-wait` to allow configuring the services before starting them up. We have this habit of starting services even if we never use them. Would be great to think of a way to avoid this. *** Bug 1490938 has been marked as a duplicate of this bug. *** Kaul, ovn-config is to be called by Ansible only for hosts that need OVN (in a cluster where an ovn network is defined, or where asked explicitly). Otherwise, the services are to be kept disabled. Can you check if https://gerrit.ovirt.org/#/c/81689/1/driver/scripts/setup_ovn_controller.sh helps, Mor? (In reply to Dan Kenigsberg from comment #5) > Can you check if > https://gerrit.ovirt.org/#/c/81689/1/driver/scripts/setup_ovn_controller.sh > helps, Mor? Yes. It finishes the execution without exception, but there is an error from ovs-vsctl when the services are not started. # vdsm-tool ovn-config 10.35.161.33 10.35.128.28 ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) May I ask for another try? https://gerrit.ovirt.org/#/c/81689/2/driver/scripts/setup_ovn_controller.sh (In reply to Dan Kenigsberg from comment #7) > May I ask for another try? > https://gerrit.ovirt.org/#/c/81689/2/driver/scripts/setup_ovn_controller.sh I responded in the patch review. Verified on: ovirt-provider-ovn-driver-1.2-0.20170920070358.gitea7e0b8.el7.centos.noarch This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |