Bug 1909930
| Summary: | Flows are not updated for trunk ports on VM migration for the qrouters | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Brendan Shephard <bshephar> |
| Component: | openstack-neutron | Assignee: | Slawek Kaplonski <skaplons> |
| Status: | CLOSED ERRATA | QA Contact: | Candido Campos <ccamposr> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 13.0 (Queens) | CC: | bcafarel, chrisw, ldenny, mahmad, pmannidi, scohen, skaplons |
| Target Milestone: | --- | Keywords: | Triaged, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-neutron-12.1.1-39.el7ost | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-06-16 10:58:54 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Brendan Shephard
2020-12-22 05:00:05 UTC
Hello, I have replicated this issue on one of the infra dev clusters (OpenShift running on OpenStack with Kuryr). I asked for one of the infra nodes to be livemigrated after I drained it (which only relocated one of the logging-es-data-master pods). After the livemigration, I attempted to relocate that elasticsearch pod, which attempted to start on that livemigrated node and failed. Upon checking, I found the same symptoms, to match those of this case. Any network tests (ping of default route, or api) fail. What would you like me to gather from this environment? Mohammad Thx Brendan and Mohammad for info. That clarifies things for me. At least I know where to look for the issue (networker node or neutron-server and l2population mechanism). I'm now deploying OSP-13 with dvr to try to reproduce such issue but if You can provide debug logs from the neutron server and neutron agents running on networker node where router is, that could also help me. Ahh, one more question - You told me that the router which is not reachable is centralized router. But in the sos report I see that dvr is enabled, at least on compute node. Is that intended? @slawek yes, these are centralized routers. There were other issues with DVR for Kuryr so they are manually setting the routers as centralized. One such issue i could remember is the VIP movemement on VMs with Allowed Address pairs, I believe its https://bugzilla.redhat.com/show_bug.cgi?id=1818741 so they were marking the routers as centralized rather than distributed. Confirming this as well, the customer set the routers as centralised just to be able to install OpenShift 3.11 with Kuryr while on OSP13z11. I believe a few other BZs were open to address these issues: https://bugzilla.redhat.com/show_bug.cgi?id=1819055 https://bugzilla.redhat.com/show_bug.cgi?id=1818695 Hi Slawek, Could you please advise if/when this will be merged downstream for OSP13: https://review.opendev.org/c/openstack/neutron/+/775104 Thank you. Hi, That patch was backported to OSP-13: https://code.engineering.redhat.com/gerrit/#/c/227439/ and is merged already. It is available in openstack-neutron-12.1.1-39.el7ost build. 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 (Red Hat OpenStack Platform 13.0 bug fix and enhancement advisory), 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-2021:2385 |