Current Series Release Notes


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 [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.

Bug Fixes

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

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

  • 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.

  • 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