Red Hat JBoss Operations Network 3.3 Update 01 (3.3.1) Release Notes

JBoss ON updates are cumulative. You only need to apply the latest update to receive all fixes from the previous updates for the same version.

A server update contains one or more updated server or agent or storage node components which can be applied to a JBoss ON server or agent directory. The JBoss ON system to which the update is applied must be fully installed and configured.

Changes and Fixes

Security related issues

This update includes fixes for the following security related issues:

General bug fixes or changes

This update includes the following bug fixes or changes:

Installation

The apply-updates utility included in the update archive will be used to update an existing JBoss ON server, agent, or storage node installation.

Updating a server and storage node

1. Shutdown the server and any other components controlled by the server's rhqctl command. Other components would include the JBoss ON agent and storage node installed on the same host as the server. To shutdown all components, the rhqctl stop command could be used.

2. Make a backup of your existing server installation and your JBoss ON system's database.

3. Extract the server update archive to the host machine where the JBoss ON component to be updated is installed.

4. As the same user who starts the JBoss ON components being updated, execute the apply-updates command passing in the path to RHQ_SERVER_HOME. For example:

    ./apply-updates.sh /opt/jboss/on/jon-server-3.3.0.GA
   

   If the target server directory includes a storage node installation, it will also be updated.

   If the target server has an agent installed in the directory above RHQ_SERVER_HOME, the agent will also be updated. For example, the above command would have also applied an agent update to /opt/jboss/on/rhq-agent if the agent was installed.

5. Start the server and all of its components, such as the JBoss ON agent or storage node, normally.

If more than one server or storage node is running in a high availability (HA) configuration, repeat the above steps for each server and storage node.

NOTE: In some cases, the update may introduce property or configuration script file changes that cannot safely be applied to existing user modified property or configuration script files. In such cases a new base or default file is created, with a .new file name extension, alongside the existing or user modified file. For example:

[jon-server-3.3.0.GA]$ ls bin/rhq-server.properties*
rhq-server.properties
rhq-server.properties.new

If the new or changed properties or configuration options are applicable to you, you will need to manually add or define them in their respective property or configuration file.

Updating an agent

NOTE: JBoss ON agents installed via RPM can not be updated using this process. Instead, update RPM based installations using your system's update manager.

These steps are only necessary if the agent's auto-update feature is disabled or if you want to manually update an existing agent.

Before proceeding, you should first apply the update to all servers in the JBoss ON system.

1. Shutdown the agent.

2. Make a backup of your existing agent installation.

3. Extract the server update archive to the host machine where the JBoss ON agent to be updated is installed.

4. As the same user who starts the JBoss ON agent being updated, execute the apply-updates command passing in the path to RHQ_AGENT_HOME. For example:

    ./apply-updates.sh /opt/jboss/on/rhq-agent
   

5. Start the agent normally.

Repeat the above steps for any agent in the system that must be updated.

NOTE: In some cases, the update may introduce property or configuration script file changes that cannot safely be applied to existing user modified property or configuration script files. In such cases a new base or default file is created, with a .new file name extension, alongside the existing or user modified file. For example:

[rhq-agent]$ ls bin/rhq-agent-env.*
rhq-agent-env.sh
rhq-agent-env.sh.new

If the new or changed properties or configuration options are applicable to you, you will need to manually add or define them in their respective property or configuration file.