2024.2 Series Release Notes

15.0.0-6

Bug Fixes

  • Remove record in amphora_health table on revert. It’s necessary, because record in amphora table for corresponding amphora also deleted. It allows to avoid false positive react of failover threshold due to orphan records in amphora_health table.

  • Fixed potential AttributeError during listener update when security group rule had no protocol defined (ie. it was null).

  • Fix error on revert PlugVIPAmphora task, when db_lb is not defined and get_subnet raises NotFound error. It could happen when Amphora creation failed by timeout and before it VIP network was removed. As result revert failed with exception.

15.0.0

New Features

  • The following options, to enable authentication in Redis Sentinel, have been added.

    • [task_flow] jobboard_redis_sentinel_username

    • [task_flow] jobboard_redis_sentinel_password

  • The new [task_flow] jobboard_redis_sentinel_ssl_options option has been added. This option controls SSL settings for connections to Redis Sentinel.

Upgrade Notes

  • The deprecated [amphora_agent] agent_server_network_file option has been removed.

  • The deprecated [health_manager] health_update_driver option was removed.

  • The deprecated [health_manager] stats_update_driver option has been removed. Use the [controller_worker] statistics_drivers option instead.

  • SysVinit and Upstart are no longer supported as init system in amphora instances. The only supported init system is now systemd.

  • The deprecated [haproxy_amphora] use_upstart option has been removed.

Deprecation Notes

  • The following options have been deprecated and have no effect now. These options were used by Upstart support which has been removed.

    • [haproxy_amphora] respawn_count

    • [haproxy_amphora] respawn_interval

Bug Fixes

  • Fixed an issue updating listeners when using SR-IOV VIP ports.

  • Fixed a bug in the VIP SR-IOV implementation that would cause load balancer memebers that use the SR-IOV VIP interface to not receive traffic.

  • Fixed error on update UDP Health Monitor with empty “delay” parameter

  • Fixed an issue when failing over load balancers using SR-IOV VIP ports.

  • Fixed an issue when a failover reverts, a neutron port may get abandoned. The issue was logged with “Failed to delete port”, “Resources may still be in use for a port intended for amphora”, and “Search for a port named octavia-lb-vrrp-<uuid>”.

  • Fix the issue, when “limit” parameter in request less or equal 0. Now it returns resources according pagination_max_limit as expected, instead of error.

  • Added a validation step in the batch member API request that checks if a member is included multiple times in the list of updated members, this additional check prevents the load balancer from being stuck in PENDING_UPDATE. Duplicate members in the batch member flow triggered an exception in Taskflow. The API now returns 400 (ValidationException) if a member is already present in the body of the request.

  • Fixed an issue when filtering resources with a boolean attribute in the GET calls in the Octavia API.

  • Fixed a bug when creating a load balancer and a listener with allowed_cidrs with the fully-populated load balancer API, the call was rejected because Octavia could not validate that the IP addresses of the allowed_cidrs have the same family as the VIP address.

  • Fix load balancer stuck in PENDING_DELETE if TLS storage unavailable or returns error

  • Fixed a bug with the nopreempt option in keepalived. The option didn’t work properly because the default role of the MASTER amphora was set. Removing the default roles from the configuration files fixed that issue. Now after a failover, the newly created amphora doesn’t preempt the MASTER role from the other amphora.

  • Added a workaround that prevent the listener PUT API call from failing if haproxy crashes during a reload. The amphora-agent ensures that in case of crashes, haproxy is correctly restarted and ready to accept incoming requests (see https://bugs.launchpad.net/octavia/+bug/2054666)