-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
1
-
rhel-net-perf
-
0
-
False
-
False
-
-
None
-
_N&P-Refined_
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Goal
The layered products use FRR more and more and more customers depend on this component. Recent buggy version of FRR that we released on the RHEL side showed that some form of better testing might be a good idea. I was contacted by folks from OCP with a couple of ideas on how to improve that. There are two things that I would like to focus on right now:
- Test FRR releases that go back to RHEL-9.4 and RHEL-9.6 (versions of RHEL that are closely tied with versions of OCP) on the OCP pipelines as well. Right now I don't have a better idea than simply build scratch builds for these versions and let them run these on the pipelines to see if it passes. I will figure out a better and automated way to do this in the future.
- Run topotests from the Upstream somewhere in our infrastructure as well. topotests are topology testing suite directly from the Upstream but the tests are not being run during build due to heavy dependency load. I will investigate what is needed to run these tests and create an extra test in our testing suite to run these in Fedora and RHEL.
Acceptance criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- We have an established pipeline in versions of RHEL that are relevant to specific versions of OCP where if a new version of FRR is being prepared to be released, it will trigger their testing pipeline and give us the green light to proceed
- We have topotests running on each build alongside other tests both in Fedora AND RHEL.