The release for Project Clearwater sprint "Wartortle" has been cut. The code for this release is tagged as release-116 in GitHub.
This release includes the following bug fixes: * Sprout became unresponsive, apparently due to a deadlock when processing CANCELs (https://github.com/Metaswitch/sprout/issues/1704) * Sprout seg-faults in some CANCEL flows (https://github.com/Metaswitch/sprout/issues/1699) * Sprout S-CSCF cannot handle Route header URIs with "scscf" in the user-part (https://github.com/Metaswitch/sprout/issues/1696) * Inconsistent behaviour on attempting to reuse a failed transport (https://github.com/Metaswitch/sprout/issues/1679) * Blocking a HSS's connection to one Homestead VM from a duplex pair causes registrations to fail for 30 seconds (https://github.com/Metaswitch/sprout/issues/1658) * Misconfigured Sprout hostname in shared_config causes nonsense error (https://github.com/Metaswitch/sprout/issues/1631) * Number-related BGCF logs say "routing directly", but that concept doesn't make sense (https://github.com/Metaswitch/sprout/issues/1611) * Sprout hanging while quiescing when updating (https://github.com/Metaswitch/sprout/issues/1530) * Sprout might never restart (race condition) (https://github.com/Metaswitch/sprout/issues/1326) * REGISTERS fail with THRIFT_EAGAIN errors with 50ms latency between GR sites (https://github.com/Metaswitch/homestead/issues/420) * homer and homestead-prov can't run on the same node (i.e. the AIO node is broken) (https://github.com/Metaswitch/crest/issues/333) * Monit fails to start Homer even though it's not running (https://github.com/Metaswitch/crest/issues/305) * The restore_backup script doesn't work when run in the signaling namespace (https://github.com/Metaswitch/clearwater-cassandra/issues/122) * Monit doesn't restart an unresponsive Cassandra process (https://github.com/Metaswitch/clearwater-cassandra/issues/118) * Cassandra failure with more than one Cassandra node (https://github.com/Metaswitch/clearwater-cassandra/issues/117) * /etc/libnss-ato.conf differs from the version installed by dpkg (https://github.com/Metaswitch/clearwater-infrastructure/issues/415) * `sudo service clearwater-infrastructure restart` gives a warning about clearwater-decommission.sh (https://github.com/Metaswitch/clearwater-infrastructure/issues/399) * Enterprise MIB alarms do not display the hostname of the node raising the alarm (https://github.com/Metaswitch/clearwater-snmp-handlers/issues/170) * astaire can deadlock with clearwater-cluster-manager (https://github.com/Metaswitch/astaire/issues/76) * Astaire doesn't handle the memcache quit command (https://github.com/Metaswitch/astaire/issues/72) * Service usage lists force-decommission, but this is not a valid option (https://github.com/Metaswitch/clearwater-etcd/issues/396) To upgrade to this release, follow the instructions at http://docs.projectclearwater.org/en/stable/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. Seb
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
