Red Hat JBoss Operations Network 3.3 Update 04 (3.3.4) Release Notes

Updated

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.

NOTE: Beginning with JBoss ON 3.3 Update 03, the `apply-updates` command can be used to apply an update to a JBoss ON server or storage node that has not yet been installed.
IMPORTANT KNOWN ISSUE: Before applying this update to your JBoss ON 3.3 server, please review the following known issues as one or more items may impact you.

Changes and Fixes

This update includes all fixes and changes from Red Hat JBoss Operations Network 3.3 Update 03.

This update includes fixes for the following security related issues:

ID Component Summary
CVE-2015-0225 Server Cassandra: remote code execution via unauthenticated JMX/RMI interface [jon-3.3.0]

General bug fixes or changes

This update includes the following bug fixes or changes:

ID Component Summary
This content is not included.BZ-1243545 Server Assigned resource group list cleared when using group assignment search function [details]
This content is not included.BZ-1259555 Server Changing the Storage Node JMX port does not update the JMX connection URL
This content is not included.BZ-1252136 Server Initial drift definition snapshot is not taken and breaks drift [details]
This content is not included.BZ-1035481 Server Port 9999 is already in use or unavailable when starting/installing/upgrading This content is not included.[details]
This content is not included.BZ-1234912 Server Do not authenticate against new storage node when replication_factor of system_auth keyspace is wrong
This content is not included.BZ-1252458 Server Rebase container upon EAP 6.4 update-03
This content is not included.BZ-1244941 Server Group inventory pages (compatible, mixed, all) fail to display groups due to UI timeouts
This content is not included.BZ-1265309 Server Operations running longer than 24hours should not be considered as not started
This content is not included.BZ-1232847 Storage Node Increase timeout for repair operation
This content is not included.BZ-1230411 Plug-ins Storage node results in 1000s of configuration changes filling up the database [details]
This content is not included.BZ-1212407 Installer/Upgrade RejectedExecutionException during installation of JON server which has been previously patched
This content is not included.BZ-1256329 Installer/Upgrade JON upgrade from 3.3.2 to JON 3.3.3 does not remove files introduced with JON 3.3.0 upgrade 02 [details]
This content is not included.BZ-1234651 Other Remove unsupported alert-scripts/README.txt and alert-scripts/example.rb files from product distribution [details]
This content is not included.BZ-1247311 Other The patch will fail on windows when it is trying to copy files with too long paths due to windows path length limitation [details]
This content is not included.BZ-1251503 Provisioning/Bundles Creation and group association of bundle fails with IllegalArgumentException: Token did not result in valid file when deploy.xml uses rhq handover [details]
This content is not included.BZ-1252142 Provisioning/Bundles Creation and group association of bundle fails with timeout followed by IllegalArgumentException: Token did not result in valid file [details]
This content is not included.BZ-1255821 Remote Client API/CLI Expose deleteBundleDestination for BundleManagerRemote in JBoss ON CLI [details]
This content is not included.BZ-1258870 Remote Client API/CLI It is not possible to delete events using JBoss ON CLI [details]

Installation

The apply-updates utility included in the update archive will be used to update a 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 a server or storage node that has not yet been installed

The update can be applied to a JBoss ON server or storage node prior to executing the rhqctl install or rhqctl upgrade command. This allows installer and upgrade specific fixes to be applied to the JBoss ON components prior to performing the installation.

  1. Extract the JBoss ON server archive as instructed in the installation guide.

  2. On the same host, extract the server update archive.

  3. As the same user who will be starting the JBoss ON components, 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 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 had already been manually installed.

  4. Perform the server, storage node, or agent installation or upgrade as instructed in the installation guide.

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.

Product(s)
Category
Tags
Article Type