This patch is fixing the code which retrieves the datapath type of
the integration bridge. The query to the OVS IDL was never executed
and the comparison was wrong, hence failing to determine when
to apply the iptables rules on DPDK scenarios introduced by [0].
[0] 26a30a3b78
Related-Bug: #1904871
Signed-off-by: Daniel Alvarez Sanchez <dalvarez@redhat.com>
Change-Id: I25147f676a5f22536888e72f21deee23c13063b6
In some of the UT for keepalived module, this check function wasn't
mocked so tests were failing on node where keepalived was actually
installed and was supporting "no_track" option.
Closes-Bug: #1913280
Change-Id: I0d20186a69d884b0b7912838f28d401ce4610d29
Apply qos resource extend func for a full list of ports,
not for each port individually, thus avoiding DB queries for each
individual port.
This should drastically improve port list time in case of many
ports/network with QoS policies assigned.
Change-Id: I1d0b3975ae6e92e34e9da20a0e26ce024422d332
Closes-Bug: #1905726
In order to support OVN migration to OSP 16.2 we need to include
this option into OVN migraiton plugin spec file.
Change-Id: Ib52052d9a178a9246a83963cfa8e2c297ee0d94f
Closes-bug: #1912948
This commit updates the network IP availability policies to understand scope
checking and account for a read-only role. This is part of a broader series of
changes across OpenStack to provide a consistent RBAC experience and improve
security.
Change-Id: Ia965e549ec5d8b23e837b41c304004d8e57785e9
This commit updates the policies for floating IP pools API
to understand scope checking and account for a read-only role.
This is part of a broader series of changes across OpenStack to
provide a consistent RBAC experience and improve security.
Partially-Implements blueprint: secure-rbac-roles
Change-Id: I60dea66e2ba6f5f450e3eae3f67f721c35940e92
This commit updates the policies for agents API to understand scope
checking and account for a read-only role.
This is part of a broader series of changes across OpenStack to
provide a consistent RBAC experience and improve security.
Partially-Implements blueprint: secure-rbac-roles
Change-Id: I28972b2c07d406b2719726e1713ce81be915f5a7
This commit updates the policies for flavor API to understand scope
checking and account for a read-only role.
This is part of a broader series of changes across OpenStack to
provide a consistent RBAC experience and improve security.
Partially-Implements blueprint: secure-rbac-roles
Change-Id: I0176702a6ec4ac69775e2ecaf4b3a94552bfe486
This commit updates the QoS policies to understand scope checking and account
for a read-only role. This is part of a broader series of changes across
OpenStack to provide a consistent RBAC experience and improve security.
Change-Id: I62eb090cb42fad54e1baa8e282b41fe2fd471b0e
The main idea of the commit is to fix code
according with the latest oslo.i18n requirements
https://docs.openstack.org/oslo.i18n/latest/
1. removed log translation if log is not seen by users
in raised exception or api call response.
2. keep translated log if it's used in raised exception.
3. removed log message 'Error while reading %s'
which was "dead" (unused) code in the function
"_get_value_from_conf_file"
of module "agent/linux/dhcp.py".
Partial-Bug: 1600788
Change-Id: Ifb5455336b06c2c87a930b816c90b4a766856b1e
When new port is created dhcp agent checks if IP addresses which are
assigned to that port aren't already associated with different ports
which are in agent's cache.
When it finds such duplicate IPs, resync of the network is scheduled.
The problem is that debug message which informs about such duplicate
IPs isn't very "verbose".
With this patch it will log new and cached port ids as well as ip
addresses on both of those ports. That should make easier to understand
why such duplicates are in the cache.
This patch also adds logging when methods like
_{network|subnet|port}_{create|update|delete} are called and with what
arguments exactly. This should help investigation what exactly happens
with some specific port in the dhcp agent.
Related-bug: #1828423
Change-Id: I964a3d843aeedef424a4466932bf702ea1b4320e
We don't need to run e.g. functional, fullstack and all scenario jobs
on patches which are changing e.g. only documentation or release notes
or other things like that.
This patch also removes test-requirements.txt and requirements.txt files
from that list of unrelated files as we want to run our ci jobs when
requirements are changed.
Change-Id: I7950de04c497b14d9225abe6584b7bb7d056f79c
To use less infra resources by every Neutron patch, let's move
co-gating jobs, like Ironic, Openstacksdk and Tripleo based jobs
to the periodic queue.
Those jobs will be still run daily so we should have pretty good
coverage if (and when) some neutron change broke those projects but
we will use less infra resources by running jobs for every patch
proposed to Neutron.
Change-Id: I91c55c9151a11401bd3a7fbe94e378a027bc97df
In case a lrp port binding event fails, report the lrp ID to help
the debugging process.
Change-Id: Ib53d39b317aae36bbb746d260442b7a132355425
Related-Bug: #1912369
Fixes broken functional tests where NamespaceFixture is used and
the TestTimer raises TestTimerTimeout even if the namespace was cleaned
up in time.
The fix makes sure that the alarm is cancelled in __exit__ if there
was no alarm before TestTimer's __enter__ (if self._old_timer is 0).
It also makes sure to reset the signal handler if the old one was
Handler.SIG_DFL (which is treated as false, no we need to check for
"is not None" instead).
Closes-Bug: #1912320
Change-Id: I9efad8eb5fe6e794235280f8a9a026800513d969
To give some relief to Zuul resources, lets move non-voting
jobs which are broken and failing all the time to the experimental
queue for now.
We can bring them back to check queue when we will fix them.
Change-Id: I4c4dd7a17ea7cc483bb4b3ed7cff7ee91f917ed9
