Security Group: limit returns in get_bridge_physdev to 1#3648
Conversation
da0d06a to
862fb5f
Compare
GabrielBrascher
left a comment
There was a problem hiding this comment.
Code LGTM, thanks @RPDiep!
|
Rebased against 4.13 as requested by @GabrielBrascher |
|
@RPDiep @GabrielBrascher |
|
I'm sure this is something now on the hypervisor, but it appears that corner cases exist in which a second line appears. As we only need one result, I added the Here's the output you requested (I added the vnet filter) |
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-325 |
@RPDiep thanks . this change looks good to me. |
|
Thanks for confirming the change and tests. I'll merge this. |
We've encountered a corner case where bridge -o link show returned two lines per bridge instead of one. get_bridge_physdev in security_group.py returned bond0.701\nbond0.701. Although this may very well be something on the hypervisor, we should limit the lines returned. I therefore added a mere | head -1 to the function.
Description
We've encountered a corner case where
bridge -o link showreturned two lines per bridge instead of one.get_bridge_physdevinsecurity_group.pyreturnedbond0.701\nbond0.701.Although this may very well be something on the hypervisor, we should limit the lines returned.
I therefore added a mere
| head -1to the function.See output:
Old:
New:
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
Tested function from idle:
Please let me know if you want me to rebase against 4.13 .