This patch fixes a revert method that was not handling extra parameters
being passed to it.
It also adds a hacking check to make sure this does not happen in the
future.
The patch also breaks the bad habit of compiling regex strings for every
line of code in the project.
Change-Id: If29e377204432e215bfea97f9d76bce0a442f4c8
Configures the octavia devstack plugin to use devstack's setup_logging
function to standardize the octavia gate log format.
Octavia processes will now print the version string to the logs on startup.
Change-Id: I094636a983fb0bcac2a1a1445b3487eac88a5e75
Closes-Bug: #1694588
Octavia v2 API was failing to create the load balancer when the user
specified a VIP port ID.
This also improves the user experience when specifying a VIP address.
It also removes the un-used nova_network directory.
Change-Id: I8b533094df1e5425f824fff0454335709ce05447
Closes-Bug: #1709922
If the lb security group contains 1 rule without protocol, worker may
raise error in _update_security_group_rules when listener creation.
Change-Id: Idc826d251296435119ae963c832de29160062967
Right now the vip data isn't actually stored back to the DB, it just
looks like it is... So, actually it will create a port and then orphan
it, then create another port with a different IP later.
Change-Id: Ibb7b2bd89155e37fb41a5f62ba2cda6e233a127a
Tempest is making credentials_factory as stable interface
and will be removing the AdminManager class which is wrapper
of creating client manager wirth admin cred.
admin manager can be instantiated by providing the admin cred
to clients.Manager.
This commit removes the usage of AdminManager.
Change-Id: I321a7985a60ceb0c6230d04e42c2b4c0a804027f
Now that all objects have a proper provisioning status, update the revert
methods to properly set the provisioning status to error.
Change-Id: I74e44474e7cd05979f2a9ce24143641230e4b394
Closes-Bug: #1624166
The health manager was marking the load balancer as ONLINE even though it was
admin_state_up == False because it was getting a health heartbeat.
This patch causes the load balancer operating status to reflect the admin
state.
Change-Id: Id0fa51447789f5ab190463a3ee0775a8612551ab
Closes-Bug: #1695323
In case the same resource is deleted twice on the amphora
ignore the 404 -- normally this should be covered by our
API logic to only allow exectly one delete but this adds
an additional fail safe.
Per johnsom's suggestion also handle that on the amphora
level.
Closes-Bug: #1705764
Change-Id: I2c5f2a4719c405d5a24acf76db40a90da67d8d17
This is *one way* to handle this problem (arguably the "correct" way).
By actively updating the status of members that don't report, we can set
disabled members to OFFLINE exactly when this becomes true.
Change-Id: I908879470e5b7767711c1234063e7959aa6055ef
Closes-Bug: #1706828
Michael Johnson
OpenStack Release Bot