openshift-ci[bot]
commented
3 months ago Hi @mtomaska. Thanks for your PR.
I'm waiting for a openstack-k8s-operators member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
softwarefactory-project-zuul[bot]
booxter
mtomaska
Openvswitch(ovs) update requires special attention in respect to the rest of the update on a edpm_node.
The OVS update must not stop and/or restart ovs services in order not to disturb the dataplane networking. If "restart" is required, it must be done via the
systemctl reloadoption, which would trigger OVS builtin mechanism that allows reloading OVS services without disturbing already present Openflows on the edpm node. By default , we do not reload on update but theedpm_ovs_reload_after_updatecan be overwritten to reload if desired.NOTE about molecule testing: This PR contains the first multi-scenario non-containerized test. Up to now, non-containerized tests contained a single
defaultscenario which was run as a separate Zuul job. Currently, the ci-framework does not support running multi-scenario molecule tests. There is work is captured in JIRA-7812 to support it. As a stopgap, this PR includescleanup.ymlplaybook which should cleanup the test instance between each scenario run.JIRA: OSPRH-6141