This document is compatible with infinity lineage assets. For more information, see ServerTemplate Lineage and Methodology.
Notice: This is a maintenance release for v13.4. Read below for more information.
Reminder: Additional release notes found here.
Table of Contents
Release Date: July 12th, 2013
Release Time: Close of business (Pacific Standard Time)
Release Highlights:
Contact Information:
docrequests@rightscale.com - Report any perceived errors, omissions, or suggestions to improve this document.
Terminology:
- Disclaimer -
The following new ServerTemplates have been added to the RightScale MultiCloud Marketplace. Be sure to read the documentation, follow best practice principles, and thoroughly test any new functionality before making any changes to your production deployment.
This is a maintenance release for infinity ServerTemplates. These release notes include the newest revisions of the v13.4 infinity ServerTemplates. See below for links to these ServerTemplates as well as information of what changed.
If you already imported the v13.4 infinity ServerTemplates, they are forward-compatible with the new revisions. Simply upgrade your revision to the newest in your account library.
The ServerTemplates listed below were all updated with the following issues listed below:
NOTE: If a ServerTemplate is not listed below, it does not have a maintenance release version.
The following ServerTemplates and MultiCloud Images can be found in the RightScale MultiCloud Marketplace. Navigate there from either:
Newest infinity version: v13.4
MultiCloud Marketplace: http://www.rightscale.com/library/server_templates/Database-Manager-for-PostgreSQ/lineage/17144
Changes:
Change | Infinity Maintenance Version | Publish Date |
---|---|---|
Snapshots improperly deleted fixed | v13.4.1 | July 12th, 2013 |
rightscale_tools gem times out while waiting for pg_start_backup() lock* | v13.4.2 | July 19th, 2013 |
rightscale_tools gem times out while waiting for pg_start_backup() lock* | v13.4.3 | August 1st, 2013 |
*v13.4.2 did not completely resolve the issue, but was verified to work as expected in v13.4.3.
Known limitations:
Newest infinity version: v13.4
MultiCloud Marketplace: http://www.rightscale.com/library/server_templates/Storage-Toolbox-v13-4-1-/lineage/7843
Changes:
Change | Infinity Maintenance Version | Publish Date |
---|---|---|
Snapshots improperly deleted fixed | v13.4.1 | July 12th, 2013 |
Known limitations:
Newest infinity version: v13.4
MultiCloud Marketplace: http://www.rightscale.com/library/server_templates/Database-Manager-for-MySQL-5-5/lineage/13699
Changes:
Change | Infinity Maintenance Version | Publish Date |
---|---|---|
Snapshots improperly deleted fixed | v13.4.1 | July 12th, 2013 |
Known limitations:
Newest infinity version: v13.4
MultiCloud Marketplace: http://www.rightscale.com/library/server_templates/Database-Manager-for-MySQL-5-1/lineage/8480
Changes:
Change | Infinity Maintenance Version | Publish Date |
---|---|---|
Snapshots improperly deleted fixed | v13.4.1 | July 12th, 2013 |
Known limitations:
After volume backups, a "cleanup" process starts by listing backups marked for deletion using inputs to determine how long to keep backups. A condition can be met where one of the backups marked for deletion is still "pending", resulting in the whole backup reported as failed and alerts sent out. With the fix, it will now only log the cleanup of the specific snapshot and show that the backup process was successful.
When running the db::do_primary_backup recipe, the rightscale_tools gem attempts to 'lock' Postgres using pg_start_(). This function makes Postgres write out a checkpoint and gives a consistent place to take a snapshot. This call takes a long time to complete and with the rightscale_tools gem timing out after 60 seconds, the recipe failed and left the lock in place. This issue has been fixed.
Please report issues to: support@rightscale.com
© 2006-2013 RightScale, Inc. All rights reserved.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.