Dear colleagues,

We rolled back the deployment of the 1.77 release to 1.76.1 in the RIPE DB production environment.

Even though there were no indications of problems on our internal test systems prior to the deployment of this release to the Release Candidate (RC) environment, and no users reported any problems on the RC environment, we found that one out of four servers had an issue with updates shortly after deploying version 1.77 to production.

We have rolled back to the previous release immediately, and we see no more issues with updates.

The updates for 26 objects in the RIPE Database failed. We will contact the maintainers of these objects individually.

We will of course perform root cause analysis of the problem with the 1.77 release. We plan to skip the 1.77 release and include the fix for this issue in the next full 1.78 release. This next release will be announced here when it's ready and will include a full staging period in the RC environment so that it can also be tested by you.

We are sorry if this caused any inconvenience.

Kind regards,

Tim Bruijnzeels

Assistant Manager Software Engineering
RIPE NCC




On 12 Jan 2015, at 10:41, Tim Bruijnzeels <tim@ripe.net> wrote:

Dear colleagues,

The RIPE NCC is pleased to announce the deployment of RIPE Database software release 1.77 to the Release Candidate (RC) environment.

This release includes:
 = Business rules to support the 2012-07 policy
 = A clear banner in the Release Candidate (RC) and Training web tools
 = Internal code to support resiliency improvements
 = Fixes for four infrequently occurring bugs

This release also includes the bug fix released earlier in 1.76.1:
 = Incorrectly formatted blank lines in updates were crashing the NRTM service (issue #284)

This release does not introduce any major functional changes.

Detailed release notes are published on the web site:

We invite all users of the RIPE Database to review the new release in the RC environment:

Please let us know if you find any issues. We plan to deploy this release to the production environment on Monday 26 January.

We look forward to any questions or comments you might have.

Kind regards,

Tim Bruijnzeels

Assistant Manager Software Engineering
RIPE NCC