Comment 5 for bug 1756064
Revision history for this message
| Armando Migliaccio (armando-migliaccio) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I cannot reproduce this on Rocky. [1] shows the steps I followed in order to try and reproduce the issue. Now you mentioned vhu ports, so I suspect this is with DPDK? Is this with QEMU client mode or Server mode? I must admit I don't have a clear picture of the wiring in the presence of DPDK and I don't have an environment where I can reproduce this with DPDK, but I am surprised that nova-compute's restart affects the datapath, which it shouldn't server mode. That said, it is true that the trunk metadata info are stored in the parent-port [2] and if there were to be missing [3], there might be a chance to leave things dangling. We could attempt and store data in the trunk bridge as well, but that might turn out to be inefficient, and that's probably why we left it to the posterity!
That said, I'd appreciate if you could clarify the conditions under which you observed this issue. For now I am going to mark it incomplete.
[1] http://
[2] https:/
[3] https:/