Description of problem: openvswitch is not started on a ComputeNeutronOvsDpdk role and fails osp deployment when using : OSP Role: ComputeOvsDpdk with a hybrid setup : ENV : hybrid- 1BM with 3 controller vms + 2 BM computes setup installed via osp operator link to roles used : https://github.com/openstack-k8s-operators/osp-director-dev-tools/pull/408/files OSP deployment fails with : ed": false, "cmd": "/bin/ovs-vsctl -t 5 list open_vswitch .", "msg": "ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection fa iled (No such file or directory)", "rc": 1, "stderr": "ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such f ile or directory)\n", "stderr_lines": ["ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or director y)"], "stdout": "", "stdout_lines": []} Version-Release number of selected component (if applicable): osp 16.2 rhel8.4-992 How reproducible: always
*** Bug 2124474 has been marked as a duplicate of this bug. ***
Moving to verified , fix has been tested to work
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 (Release of components for Red Hat OpenStack Platform 16.2.4), 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/RHBA-2022:8794