On change ae635b5b80fcb61c429a6fc17961a9f3bf614964, the vswitch_class
was changed to ovs_dpdk, but the resources created by sysinv at [1]
are at the platform::vswitch::ovs:: lookup. This mismatch is failing
lookup and the bridges for the underlying datanetworks aren't being
created when puppet runs. As a result, the neutron-ovs-agent pods are
failing with CrashLoopBackoff. This commit fixes it by reverting the
resources to the correct lookup path on hiera.
TEST PLAN
PASS ovs-dpdk: Clean install of the Starlingx ISO verified that the
br-phy* bridges were created for the underlying datanetworks
using ovs-vsctl on the host
PASS ovs-dpdk: Installation of stx-openstack is successful
PASS ovs-dpdk: Created project networks and instances
PASS ovs: Clean install of the Starlingx ISO
PASS ovs: Installation of stx-openstack is successful and the openvswitchd and ovs-agent pods are running OK
PASS ovs: Created project networks and instances
Reviewed: https:/ /review. opendev. org/c/starlingx /stx-puppet/ +/825398 /opendev. org/starlingx/ stx-puppet/ commit/ e00edd94f32f09f 07e45b0ee3752d0 97d3a8f844
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit e00edd94f32f09f 07e45b0ee3752d0 97d3a8f844
Author: Thiago Brito <email address hidden>
Date: Wed Jan 19 17:26:16 2022 -0300
Fix resource lookup for ovs
On change ae635b5b80fcb61 c429a6fc17961a9 f3bf614964, the vswitch_class :vswitch: :ovs:: lookup. This mismatch is failing
was changed to ovs_dpdk, but the resources created by sysinv at [1]
are at the platform:
lookup and the bridges for the underlying datanetworks aren't being
created when puppet runs. As a result, the neutron-ovs-agent pods are
failing with CrashLoopBackoff. This commit fixes it by reverting the
resources to the correct lookup path on hiera.
[1] https:/ /opendev. org/starlingx/ config/ src/commit/ ece13f740847f3b cc7470cc7ec8c18 96dd61f014/ sysinv/ sysinv/ sysinv/ sysinv/ puppet/ ovs.py# L108
TEST PLAN
openvswitchd and ovs-agent pods are running OK
PASS ovs-dpdk: Clean install of the Starlingx ISO verified that the
br-phy* bridges were created for the underlying datanetworks
using ovs-vsctl on the host
PASS ovs-dpdk: Installation of stx-openstack is successful
PASS ovs-dpdk: Created project networks and instances
PASS ovs: Clean install of the Starlingx ISO
PASS ovs: Installation of stx-openstack is successful and the
PASS ovs: Created project networks and instances
Closes-Bug: #1958073 c7f82b8e67e3e5d 18a2103d599
Signed-off-by: Thiago Brito <email address hidden>
Change-Id: I53e16df5403fa7