Align failover_amphora and failover_loadbalancer to use
run_flow.
Also avoid NoneType error in logging of create_health_monitor.
Change-Id: I1b4c18d3bec5ff62adf48d3d751d553eb359ccbe
In what appears to be a race condition, load balancer cascade delete can
fail while deleting numerous pools. The load balancer can still be
deleted with one or more follow-up cascade delete API calls but this is
suboptimal.
Per local testing, the ValueError exception is harmless so we can just
ignore it and continue the pool delete flow, with no orphan resources
left behind resulting from the exception skip.
Task: 41096
Story: 2008249
Change-Id: I9283d9804feb83a1d5a160da48da6146b19da88c
requirements.txt is unnecessary when run tox -e releasenotes,
releasenotes relative stuffs is in doc/requirements.txt
Change-Id: Ia6649ba95bdaa5d4c48f766bc8c1a87bab4f07b3
There was a bug in the load balancer failover code for the amphora
v1 driver where if there were multiple failed amphora, with session
persistence, could cause a load balancer failover to not complete.
Change-Id: Ia46a05ab9fdc97ed9be699e5b2ae90daca3ab9a2
Story: 2008099
Task: 40802
Add file to the reno documentation build to show release notes for
stable/victoria.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/victoria.
Change-Id: Ibc14026c757b424c36dc2b1ed356c2e62e36499e
Sem-Ver: feature
Change I612ea1c583090897bd44453b867d75929a01b7fc [1] removed
diskimage-builder from the root requirements.txt file. Devstack
deployments not setting LIBS_FROM_GIT+=diskimage-builder will not
install diskimage-builder. This means our diskimage-create.sh tool will
fail to build amphora images and abort the deployment.
[1] https://review.opendev.org/#/c/741960/
Change-Id: Id535d2d5ea6c23c9646c568a17d7695f82c0c1a9
Deleted amphorae should not be included when housekeeping service is
performing certificate rotation. Otherwise, deleted amphorae will
become ERROR.
Story: #2007635
Task: #39681
Change-Id: Ie2c748ff69c8fd736e9c67d686068a33d803222e
Ubuntu 20.04 is a "Tested Runtime" for the Victoria release[1].
This patch updated our diskimage-create script and elements to
support building a amphora image that uses Ubuntu 20.04 (focal).
[1] https://governance.openstack.org/tc/reference/runtimes/victoria.html
Change-Id: I6f53ea5d012ab64b985d981ecd1b1967e18e4e81
The original patch: Ib2a80afb9223da2c0af6f6add250ffaaa20a316f
First attempt at fixing this issue assumed that the update function
would actually be called again after the initial LB creation, which it
is not. We should ensure that this is called when we do any UDP listener
creation, so the file can be removed if necessary.
Change-Id: Iec1ec7df420e3746b47004c8c0374d2d8274f45b
The API list methods were not handling unscoped tokens correctly.
If the API is using the admin_or_owner-policy.yaml policy override file,
and a user used an unscoped token, the API will list objects for all
projects. This patch corrects that issue.
If you are using the default policies, the API handles unscoped tokens
correctly.
Change-Id: I88e64fd5e8a4c709f735be85b85139dbb52e4acd
This patch adds a new tox environment and gate job that checks
requirements.txt for missing or extra requirements.
Change-Id: Id8c44821455644576cf055cccaa38c9ab2f49ec6
There are a couple of extra requirements no longer used and one
that was missing. This patch corrects that.
Change-Id: I5f45e6f0f15bca201c3ef63f2e42a183510f5977
In amphora-agent API version 1.0, backend certificate files are uploaded
to /var/lib/octavia/certs/<lb_id>/. However, the "server" line in the
rendered HAProxy configuration sets the certificate paths to
/var/lib/octavia/certs/<listener_id>/ (amphora-agent version 0.5).
This renders an invalid HAProxy configuration file and as result HAProxy
fails to reload with the new configuration, and members marked in ERROR
provisioning status.
Task: 40903
Story: 2008157
Change-Id: I7e2b12f19ee7b172464e809df6342ade1e87fb2e
This patch fixes an hidden AttributeError exception in the HAProxy
driver when adding TLS-enabled pools to listeners.
Task: 40895
Story: 2008150
Change-Id: If165e995a8b61d8a8ed6bc0c4dd036af0c55c6e0
This patch removes an unnecessary joinedload when looking up a
load balancer from an amphora ID. This should reduce the database
load when this method is called.
Change-Id: I04bb38c657c87ace941eb6e332f58f7218980ad1
A previous patch[1] forgot to update the api-ref protocol combination
tables for the PROXYV2 pools.
This patch corrects that oversight.
[1] https://review.opendev.org/747801
Change-Id: I84025c5d1d3091c408416fb78b92ae0a7a89b74e
There is a bug in the octavia-lib DIB element where it runs install
actions that should only be ran when the amphora-agent is installed from
source. This issue causes the amphora image build to fail when
installing the amphora-agent from distribution packages (option -p in
the diskimage-create.sh tool).
Task: 40870
Story: 2008138
Change-Id: I46ba7798322f24255ab7d49db4b4df886e92cbf3
This patch updates the tempest plugin regex for the grenade job
to run the tests tagged with the "smoke" attribute.
Change-Id: Id1eadc19dd283caeb9f6a31dc69e5bc734daf784
This file is created when no HAProxy listeners exist so VRRP will fail,
but needs to be removed when a UDP listener is added so that VRRP can
actually correctly start.
Story: 2008133
Task: 40859
Change-Id: Ib2a80afb9223da2c0af6f6add250ffaaa20a316f
diskimage-builder is already listed in diskimage-create/requirements.txt,
and it isn't really a run-time dependency for octavia so it tends to be
confusing downstream as we generally add run-time dependencies based on
the root requirements.txt.
Change-Id: I612ea1c583090897bd44453b867d75929a01b7fc
Story: 2007934
Task: 40389
The pyroute2 module had a regression in 0.5.13, but neutron needed a fix
that was included in 0.5.13. It was easier for us to work around it than
for neutron to revert the update to 0.5.13, so we hacked a workaround[1].
A new pyroute2 release, 0.5.14, has been published, so this patch reverts
the hack and bumps our minimum version of pyroute2 to 0.5.14.
[1] https://review.opendev.org/#/c/744045
Change-Id: Ia4357a4f5db07e1a6b0beb11b58ce125215eeef1
In an amphora failover situation, if the VRRP port of the other
amphora in an active/standby pair is missing from neutron, the amphora
failover may fail with a "port not found" error.
This patch corrects this issue by allowing the amphora failover in
progress to complete even if the other amphora is also in a failed
state.
Story: 2008127
Task: 40851
Change-Id: I806d220236ad741b638ad9315537334f2d923031
