Red Hat JBoss Operations Network 3.3 Update 08 (3.3.8) 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.

Changes and Fixes

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

General bug fixes or changes

This update includes the following bug fixes or changes:

ID Component Summary
This content is not included.BZ-1415511 Server Security Hardening - Prevent Deserialization Attacks from using Groovy MethodClosure private readObject method
This content is not included.BZ-1315314 Server BaseLineMean is set to NaN [details]
This content is not included.BZ-1369101 Server Store and key passwords incorrectly required in rhq-server.properties
This content is not included.BZ-1382649 Server Attempt to add notification for the second alert definition in UI throws message "Failed to get notification configuration preview" [details]
This content is not included.BZ-1399125 Server Attempt to list bundle versions fails with the message "Failed to find defined bundles...." [details]
This content is not included.BZ-1369085 Server Values for rhq.server.tomcat.security.client-auth-mode and rhq.communications.connector.security.client-auth-mode are not validated
This content is not included.BZ-1236021 Server Metrics summary graph is misleading [details]
This content is not included.BZ-1367505 Server Not all files are available on the Content -` New pages if total number of files exceeds the items per page setting [details]
This content is not included.BZ-1364474 Server PARTITION_EVENT_PURGE and RESOURCE_CONFIG_HISTORY_PURGE properties remain in the database after 3.3.6 [details]
This content is not included.BZ-1318747 Server When editing already created alert condition Measurement Absolute Value Threshold the base units are incorrect
This content is not included.BZ-1368107 Server Increase the amount of items per page for "Content" -` "New" page [details]
This content is not included.BZ-1323332 Server Orphaned configuration left in database
This content is not included.BZ-1272328 Storage Node Storage node in maintenance operation mode cannot be undeployed [details]
This content is not included.BZ-1368556 Agent Agent autoupgrade fails when 2-way authentication is used
This content is not included.BZ-1302800 Agent Remote agent auto upgrade failed when sslsocket encryption enabled
This content is not included.BZ-1379834 Agent EAP version identifier change results in loss/reset of plug-in configuration [details]
This content is not included.BZ-1307104 Agent "org.hyperic.sigar.win32.Win32Exception: Buffer size (8192) too small (10332 needed)" when reading Windows events [details]
This content is not included.BZ-1382041 Plug-ins Discovery of ActiveMQ fails with NullPointerException when credentials name is not set [details]
This content is not included.BZ-1366324 Installer/Upgrade A JBOSS_HOME environment variable set in the user env that is executing apply-update causes jboss-cli updates to fail when updating to 3.3.6 [details]
This content is not included.BZ-1410981 Installer/Upgrade Running apply-updates.bat with agent as target attempts to run rhqctl upgrade --apply-fixes [details]
This content is not included.BZ-1192927 Installer/Upgrade Improve permission checking for agent installed via rhqctl
This content is not included.BZ-1404820 Installer/Upgrade apply-updates.bat on Windows does not property quote/escape RHQ_JAVA_EXE_FILE_PATH [details]
This content is not included.BZ-1408321 Installer/Upgrade Update fails apply-fixes and jboss-cli steps if RHQ_SERVER_HOME is not set to the same location as passed to apply-updates [details]
This content is not included.BZ-1386913 Provisioning/Bundles Newly uploaded content results in previous content version being left in database with no way to clean it up [details]
This content is not included.BZ-1292732 Provisioning/Bundles DELETE/UNDEPLOY of resource results in associated data being left in database [details]
This content is not included.BZ-1381720 Provisioning/Bundles Uninventory of resource with content leaves orphaned LOB data in the PostgreSQL pg_largeobject table [details]
This content is not included.BZ-1381725 Provisioning/Bundles Create Child Deployment/DomainDeployment results in orphaned LOB data in the PostgreSQL pg_largeobject table [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.

Category
Article Type