DescriptionMaxim Babushkin
2018-04-24 13:19:17 UTC
Created attachment 1426059[details]
dpdk_overcloud_log.txt
Description of problem:
OSP 13 dpdk deployment fails with the error:
ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory)
Version-Release number of selected component (if applicable):
OSP 13
Puddle: 2018-04-19.2
Full overcloud log attached.
SOS report will be added shortly.
This bug is present from the day one of adding volumes support to the docker-puppet script. But it has been hidden because of the order merging the config volumes. Till earlier puddle config_volume of neutron-ovs-dpdk-agent.yaml before config_volume of neutron-plugin-ml2.yaml, in which case the volumes will be added correctly. In this puddle, config_volume of neutron-plugin-ml2.yaml is merged first, and because of the bug, volumes list in other plugin is ignored. It is hard to find what triggered the order change, but irrespective of the order, the merging should happen correctly.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:2086
Created attachment 1426059 [details] dpdk_overcloud_log.txt Description of problem: OSP 13 dpdk deployment fails with the error: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) Version-Release number of selected component (if applicable): OSP 13 Puddle: 2018-04-19.2 Full overcloud log attached. SOS report will be added shortly.