As of the Ussuri cycle, the OVN Octavia Provider Driver code has been split-out of the networking-ovn repository into it's own [0], [1]. This package/component needs to be created downstream for OSP17+ so we can both file bugs against it, as well as have the automation tools automatically pull code downstream. The default assignee I think can be as other things in the Networking DFG are, Assaf Muller. It was added to RDO here [2], spec file [3]. [0] https://review.opendev.org/#/c/697076/ [1] https://review.opendev.org/#/c/707115/ [2] https://review.rdoproject.org/r/#/c/26320/ [3] https://github.com/rdo-packages/ovn-octavia-provider-distgit/blob/rpm-master/python-ovn-octavia-provider.spec
After thinking about this, I'll probably need a different BZ to create the bug component, this one can be for creating the downstream repo.
After filing another bug for adding the component to bugzilla (bz 1894607), I was told that each product team does this themselves. Since this is still open can it be done as part of this one? Here's my cut/paste from the other bug: We started packaging a new component in Red Hat Openstack called python-ovn-octavia-provider, which now needs a bugzilla component added to better track bugs against it. Can it please be created? Product: Red Hat Openstack Component: python-ovn-octavia-provider Default Assignee: rhos-maint Default QA Contact: ekuris Brief Description: "For bugs relating to the OVN Octavia Provider Driver" Please let me know if I missed something, thanks.
Ping?
My apologies - I completely missed this. I
build included on advisory, marking verified
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 17.0 (Wallaby)), 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-2022:6543