rBuilder:Version-specific Updates

From rPath Wiki

When performing system updates in rBuilder, be sure to review the rBuilder Release Notes, and take note of the following version-specific update considerations.

Verify the Version and Update

Verify the current version of rBuilder in the footer of rBuilders rPath Appliance Platform Agent (rAPA) interface when performing appliance administration on rBuilder.

Update to 4.1.0

Starting with version 4.1.0, the conary repositories for products in rBuilder should use PostgreSQL databases instead of SQLite databases. PostgreSQL provides better performance, improved concurrency, and higher reliability. After updating rBuilder to 4.1.0, schedule a maintenance window as appropriate prior to migrating to PostgreSQL.

rPath strongly recommends you convert to PostreSQL using the provided link in the menu; until your rBuilder appliance has done this, you are in an unsupported configuration. See the Update Path to 4.1.0 section of this guide for detailed instructions and precautions about this update and migration.

Migrations to rBuilder 4.1.0 require that your current rBuilder version is of 4.0.0 or higher. If you are currently using rBuilder 3.1.4 or earlier, you must first update to 4.0.x before moving to 4.1.0. Because of major changes in the partition structure and job handling, updating to 4.1.x from pre-4.0.x releases requires a backup, new installation, and restore process as described here. Additionally, rBuilder 4.0.0 runs on 64-bit processor architectures only. Because of these changes, rPath is assisting each customer with the 3.x to 4.0.x update process.

Customers with rBuilder 3.1.4 or earlier should contact an rPath representative to schedule an update to rBuilder 4.0.1.

Update to 4.x

rBuilder 4.0.0 was released for new installations only, and rBuilder 4.0.1 and forward have an update path from pre-4.x rBuilder installations. Because of major changes in the partition structure and job handling, updating to 4.x from pre-4.x versions requires a backup, new installation, and restore process with scheduled assistance and removable storage from rPath. Please use the following page as a guide to updating to 4.x:

Update Path to 4.x

Update 3.1.3 Interim Release

The 3.1.3 Interim Release adds a new build type Update ISO. If updating from 3.1.2 or earlier, or if performing a new install of the 3.1.3 Interim Release, there is a known issue that affects this new feature. To resolve the issue and to be able to use this new build type, run the following two commands as root on the rBuilder system following the 3.1.3 Interim Release update:

echo buildTypes UPDATE_ISO >> /srv/rbuilder/jobserver/3.1.3/srv/rbuilder/iso_gen.conf 
/sbin/service multi-jobserver restart

Updates from previous 3.1.3 releases to 3.1.3 Interim Release are not impacted in the same way; contact your rPath support representative for more information about the fix for this update.

Update 2.0.x to a New Version

Update to a new version of rBA using rAA:

1. Sign in to rBA as an administrative user.
2. Click Site administration in the user panel.
3. Click Manage Maintenance Mode on the left panel and put rBA into maintenance mode.
4. Click Enter rPath Appliance Agent in the Administration Menu panel. Verify a new browser window is launched with the rAA interface.
5. In rAA, type user name admin and the rAA admin password and click Sign In. Note that the rAA admin user and password is distinct from your rBuilder administrative user.
6. Click System Updates on the left panel.
7. Click Check Now to start checking for available updates.
8. Click Apply Updates to apply the updates shown.
9. After updates are successful, start the job server and exit maintenance mode to resume rBA function.

Expect rBuilder to have service interruptions during the update.

Updating rBA from 1.6.3 to 2.0.0

An rPath field engineer must perform rBA updates using the update script described below. Note also, that this script MUST be used to update your existing version 1.6.3 rBA. DO NOT attempt to update the rBA manually by using conary commands.

You can update an existing rBuilder Appliance from version 1.6.3 to version 2.0.0 by using a script that handles the migration of the rBA software and associated repository mirrors hosted by the rBA.

To execute this script, you must use command line access.

Verify the rBA version to be sure you are working with a version 1.6.3 rBA prior to executing the migrate script. If your version of rBA is earlier than 1.6.3, contact rPath for information on updating to rBA 1.6.3 and beyond.

After verifying your existing rBA version is 1.6.3, follow these steps to update your rBuilder Appliance to version 2.0.0:

1. Execute the migration script.
2. Update entitlements.

Execute the Migration Script

Execute the migrate-rba-1.6-to-2.0.sh script to initiate the update and migration:

[root@localhost ~]# ./migrate-rba-1.6-to-2.0.sh

If your rBA has a full rPath Linux local mirror the migration process can require a considerable amount of time.

During the migration process, you may see error messages resembling the following. These messages are innocuous and may be ignored:

Exception exceptions.AttributeError: <exceptions.AttributeError instance at 0xb7461b4c> in <bound method Connection.__del__ of <conary.sqlite3.main.Connection instance at 0xb745bf8c>> ignored

After the script completes successfully, rBA services are restarted.

Update Entitlements

The last step required for this update is to refresh the rBA's entitlements using the rPath Appliance Agent (rAA), the previous name of the rPath Appliance Platform Agent. Sign in to the rAA web interface, access the entitlement management function and update the entitlements according to this process:

1. Sign in to the rBA as an administrative user.
2. Click Site administration in the user panel.
3. Click Enter rPath Appliance Agent in the Administration Menu panel. Verify a new browser window is launched. It is typical to receive warning messages that the certificate being used was not created by a recognized Certificate Authority, but no action is required regarding these warnings before configuring the rAA.
4. Sign in to the rAA with your username and password. At this time, you will be presented with the rPath Appliance Agent Wizard. Click OK to continue.
5. Click Done to complete the network configuration screen.
6. Click Configuration and then Manage Entitlements.
7. Click OK to refresh the entitlement.
8. Sign out of the rAA interface and close the browser window.

Alert for 1.6.3 and Prior Versions

The crontab:runtime component was arbitrarily excluded in prior versions of rBA. This is not an issue after updating to 2.0.0. If you have version 1.6.3 or prior, use the rBA command line access to check to see if crontab:runtime is installed using the following command:

conary q crontab:runtime

If the command returns no data prior to the next command prompt, or if the command indicates the component was not found, install the component using the following command.

conary update crontab:runtime

The update command should install the component from the appropriate repository indicated by your install label path. If you have issues installing crontab:runtime, contact rPath for support.