This change proposes a ML2 plugin extension to implement tagging during
bulk port creation.
Change-Id: Ic70f7d282db478c69016ab1c317c5cae786401ce
Related-Bug: #1815933
The create ports in bulk code in the ML2 plugin is passing to the
extension drivers a DB object for each port created. Per the ML2
extension drivers API definition in [0], what should be passed instead
is the result dictionary of each created port. This change fixes the
mismatch.
[0] 478502b3df/neutron_lib/plugins/ml2/api.py (L1142)
Change-Id: I6abecfbde525279fbfd4b9e27e0d1803311a7f96
Only if ARPSpoofTestCase is correctly initialized (there is no error
in setUp method), the exception handler "collect_flows_and_ports" can
be executed in case of error. This method needs to have some declared
members during the test case setup.
Trivial-Fix
Change-Id: Ic087adc3e38f33cf369f04ec7b78db0b72134673
The neutron-ovn-base had the "tempest_concurrency" set to 2, which is
halve the value from other tempest jobs.
This patch changes it to 4 to speed things up and to match with the rest
of the jobs in neutron.
Change-Id: I7be206006f8c035b983bac8ef34f937e64734bb9
Signed-off-by: Lucas Alvares Gomes <lucasagomes@gmail.com>
As seen in the reported bug, in heavy loaded CI systems, the Neutron
openstack-tox-py3{6,7} and openstack-tox-lower-constraints jobs tend
to timeout.
Change-Id: I3f7aff297e8c1797eb23adac7b29dc65619c1e8a
Closes-Bug: #1860332
This job can't run on python 3 and it's failing 100% since long time.
There is no point to run it like that now as it's only waste of infra
resources.
We will re-add this job to Neutron's check queue when it will be fixed.
Change-Id: Id5b8fc484112e16c7b627b38af3440f1ce387ffb
Right now neutron-server bumps the nb_cfg parameter in NB_Global
table which needs to be propagated by northd to SB_Global,
processed by agents, and write it back into SB_Global.
This requires processing by neutron-server but unfortunatelly
the server checks straight away and many times the value read
is behind the expected value.
All this results in frequent false positives showing dead agents
when they are not.
This patch is relaxing the checks by allowing a difference of 1
between the read and expected values.
Change-Id: Id91481b690ad569c5dcfa5bd404f497f591d729d
Closes-Bug: 1860436
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
Assign local variable "interface_name" before being referred in
"TestL3Agent._router_fip_qos_after_admin_state_down_up"
Change-Id: I5135f5c7c02b25728d2d8843889b9e8aef1265cd
Closes-Bug: #1860209
This patch adds info about always bumping minor version number if
e.g. OVO object version was changed in stable release.
That should at least increase awarness of operators that some special
care is needed during update.
Change-Id: I3fc88158e793b4a4bb4e7a43f106291857b2eb74
For now while updating FIP check if port or logical_ip
has changed and only then we deleted the NAT entry.
Unfortunately each time when FIP update occurs the
method _create_or_update_floatingip() is used. It first deletes
LSP pointed by FIP and adds it again along with new NAT entries.
Based on author comment this actions are required.
So if we don't update FIP with logical_ip or new port_id,
like update a description, the NAT entries gets duplicated.
Since all is wrapped withing a transaction and to not wait for
proper fix (this code need sa refactor based on commments with NAT
external_id column) I think thats safe just to delete the NAT entry
in such situation like described above.
Change-Id: Iea532e2a02b7992305d1b90aa040e064901c340c
Related-Bug: #1859977
Usually Neutron stops neutron-keepalived-state-change-monitor process
gracefully with SIGTERM.
But in case if this will not stop process for some time, Neutron will
try to kill this process with SIGKILL (-9).
That was causing problem with rootwrap as kill filters for this process
allowed to send only "-15" to it.
Now it is possible to kill this process with "-9" too.
Change-Id: Id019fa7649bd1158f9d56e63f8dad108d0ca8c1f
Closes-bug: #1860326
This context was required but not passed. This change adds it.
Change-Id: I5e5e14d5a621fc4a790810d15e1162f90898282e
Related-Blueprint: neutron-ovn-merge
This patch is re-enabling test_port_security_macspoofing_port as the
referrenced bug should be fixed already.
Change-Id: I138d16055f460e20678bb8f76d5c64e6565063ea
Related-bug: #1728886
Signed-off-by: Daniel Alvarez <dalvarez@redhat.com>
"OVNMechanismDriver._create_security_group_precommit" receives the
notification from [1]. The aditional arguments passed are kwargs
and the position is not guaranteed.
[1]79cb971251/neutron/db/securitygroups_db.py (L137-L140)
Change-Id: I049523ac302fda227fe2f340d3deb6a15ffdb0fc
Related-Blueprint: neutron-ovn-merge
This job can't run on python 3 and it's failing 100% since long time.
There is no point to run it like that now as it's only waste of infra
resources.
We will re-add this job to Neutron's check queue when it will be fixed.
Change-Id: I7833295398686aca3c37859dbe4c1c9d2aca1c55
Miguel Lavalle