SupportConsoleDevelopersStart a trialContact

5.2. Patching a Fabric from 6.2.0 to 6.2.1

Overview

The instructions in this section are for upgrading an existing JBoss A-MQ 6.2.0 Fabric installation to version 6.2.1.
Warning
Rolling back the patch level from version 6.2.1 to 6.2.0 is not supported in JBoss A-MQ Fabric. This is a special case, because the version 6.2.0 Fabric agent does not support the new patching mechanism.

Prerequisite for patching Fabric in JBoss A-MQ

The following artifact—which is required in order to patch a Fabric with the new patching mechanism—is missing from the jboss-a-mq-6.2.1.redhat-084.zip distribution: 
system/io/fabric8/fabric8-karaf/1.2.0.redhat-621084/fabric8-karaf-1.2.0.redhat-621084.zip
Consequently, even after adding the JBoss A-MQ 6.2.1 rollup patch to your existing 6.2.0 container, this file will be missing from your 6.2.0 container installation.
This file is required in order to patch a JBoss A-MQ Fabric system. The missing file will be provided in the first patch for JBoss A-MQ. In the meantime, if you have access to the Red Hat JBoss Fuse 6.2.1 on Karaf Update Installer distribution (jboss-fuse-full-6.2.1.redhat-084.zip), you can copy the missing file from that distribution into the location given above. Otherwise, please contact support.

New patching mechanism

Upgrading from JBoss A-MQ 6.2.0 to 6.2.1 requires the new patching mechanism, which is implemented for the first time in 6.2.1. This presents a bootstrapping problem: the existing 6.2.0 installation must be enhanced to support the new patching mechanism before you can install patch version 6.2.1. The upgrade procedure therefore consists of the following distinct phases:
  1. Install the patch management enablement pack for 6.2.0, which replaces the existing patch mechanism with the new patching mechanism. In all other respects, the container remains at version 6.2.0.
  2. Install the 6.2.1 patch in the container using the new patch mechanism and create a new profile version to store the 6.2.1 patched profiles.
  3. Upgrade each of the containers in the fabric to the patched version.

Upgrading different container types

A typical fabric consists of a variety of different container types. When migrating the fabric from 6.2.0 to 6.2.1, the different container types have to be handled in slightly different ways, as follows:
Root container
The root container is the container where you initially install the patch. The root container plays a key role in the patch process—for example, by acting as a source of patch files for the other containers in the fabric. For this reason, it is recommended that you upgrade this container last of all.
SSH container
There are some special steps required to prepare SSH containers for patching. See the section called “Preparing for a Fabric SSH container upgrade”.
Child container
Because child containers share some files and configuration with their parent container, they can easily get into an inconsistent state during the patching process. The simplest way to deal with child containers is to shut them down and focus on upgrading the parent container initially. After the parent container has been successfully upgraded, you can turn your attention to the child containers.
Note
Child containers cannot be kept at a lower patch version than the root container. They must be upgraded to at least the same patch version as the parent container.

Establishing a baseline for an SSH container upgrade

The new patching mechanism keeps track of all the changes that are made as successive patches are installed (in order to be able to roll back the patches, if needed). Hence, the first step performed by the patching mechanism is to scan the existing container installation to discover its initial state (establishing a baseline for subsequent changes introduced by patches). In particular, the patch mechanism scans certain subdirectories of the system/ directory, to discover the initial set of bundles and Maven artifacts available in the installation.
In the case of the JBoss A-MQ 6.2.0 distribution (which has not been optimised to work with the new patching mechanism), a problem arises because the core Fabric distribution, fabric8-karaf-1.2.0.redhat-133.zip, is initially not included with the 6.2.0 distribution and is not present in system/. When Fabric requires a copy of this file (for example, for creating a remote SSH container), it has two alternative ways of obtaining it:
  • By downloading the missing core Fabric artifact, fabric8-karaf-1.2.0.redhat-133.zip, from a remote Maven repository.
  • By assembling the fabric8-karaf-1.2.0.redhat-133.zip file on the fly from the contents of the root container.
The differences between these two Fabric archives are minor (for example, different branding in the welcome banner) and both are supported for use in a fabric. If it has already been created or downloaded, the Fabric distribution Zip file will be stored in the following location under system/: 
system/io/fabric8/fabric8-karaf/1.2.0.redhat-133/fabric8-karaf-1.2.0.redhat-133.zip
For establishing an initial baseline, what counts are the bundles installed in the system/ directory of the root installation (the container you are using to install patches across the fabric). It can happen, however, that an SSH container uses a different version of fabric8-karaf-1.2.0.redhat-133.zip from the one that is installed in the root container. If the Fabric distribution installed in root and the Fabric distribution installed in the SSH container are different, it is impossible to establish a proper baseline for the SSH container and patching of the SSH container will fail.
The patching mechanism has been specially modified to enable a workaround for this problem. Specifically for the fabric8-karaf-1.2.0.redhat-133.zip Maven artifact (and only for this artifact), it is possible to install two different artifact versions under the system/ directory, with the following names: 
system/io/fabric8/fabric8-karaf/1.2.0.redhat-133/fabric8-karaf-1.2.0.redhat-133.zip
system/io/fabric8/fabric8-karaf/1.2.0.redhat-133/fabric8-karaf-1.2.0.redhat-133-custom.zip
Where one of the file names ends in .zip and the other ends in -custom.zip. It does not matter which file is which. When both of the alternative Fabric distribution files are stored in this way, it becomes possible for the patching mechanism to establish a baseline for either of the Fabric distributions and patching of SSH containers will now work.

Initial system

The starting point for this patching procedures is assumed to be an installation of Red Hat JBoss A-MQ 6.2.0 (jboss-a-mq-6.2.0.redhat-133.zip), which is already configured as part of a Fabric (see ).
This can be a container instance that you have customized in various ways, by adding application bundles and features, or even by editing configuration files under the etc/ directory.
Note
The new patching process is usually non-destructive, preserving any customizations made before the patch was applied. If a merge conflict cannot be resolved automatically, however, warning messages will be generated in the log file.

Download the required packages

To patch JBoss A-MQ from 6.2.0 to 6.2.1 you require the following packages:
patch-management-for-amq-620-6.2.1.redhat-084.zip
Available as the download file, Red Hat JBoss A-MQ 6.2.1 on Karaf Update Installer.
jboss-a-mq-6.2.1.redhat-084.zip
Available as the download file, Red Hat JBoss A-MQ 6.2.1.

Preparing for a Fabric SSH container upgrade

(SSH containers only) Before performing any of the steps to apply the 6.2.1 patch to Fabric, prepare for SSH container upgrades by performing the following steps (for a detailed explanation of why this is necessary, see the section called “Establishing a baseline for an SSH container upgrade”):
  1. In the installation of your root container, look for the following file under the system/ directory: 
    system/io/fabric8/fabric8-karaf/1.2.0.redhat-133/fabric8-karaf-1.2.0.redhat-133.zip
    Use a file system command to get the exact size of this file in bytes (which provides a simple way of identifying this file).
    Note
    It is possible that there is no fabric8-karaf-1.2.0.redhat-133.zip file located under this directory, which would suggest that you have not used the root container to create any SSH containers.
  2. Look for the fabric8-karaf-1.2.0.redhat-133.zip that is installed with your SSH container (or SSH containers). Use a file system command to get the exact size of this file in bytes. Repeat this for every SSH container instance in your fabric.
  3. Compare the file sizes obtained from the SSH containers with the file size obtained from the root container. If all of the file sizes are the same, this indicates that all of the containers in the Fabric are using exactly the same Fabric distribution—proceed straight to the section called “Applying the 6.2.1 patch to a Fabric container”.
    If any of the file sizes obtained from the SSH containers differ from the file size obtained from the root container, this indicates that at least one of the SSH containers is using a Fabric distribution that is different from the root container's Fabric distribution—proceed to the next step.
  4. Take one of the fabric8-karaf-1.2.0.redhat-133.zip files that is different from the fabric8-karaf-1.2.0.redhat-133.zip file already stored under the root container's system/ directory (where the difference is indicated by having a different file size), rename it to fabric8-karaf-1.2.0.redhat-133-custom.zip, and copy it to the following location under the root container's system/ directory: 
    system/io/fabric8/fabric8-karaf/1.2.0.redhat-133/fabric8-karaf-1.2.0.redhat-133-custom.zip
    When you are finished, there should be two files located under this directory, as follows: 
    system/io/fabric8/fabric8-karaf/1.2.0.redhat-133/fabric8-karaf-1.2.0.redhat-133.zip
system/io/fabric8/fabric8-karaf/1.2.0.redhat-133/fabric8-karaf-1.2.0.redhat-133-custom.zip

Applying the 6.2.1 patch to a Fabric container

To upgrade a JBoss A-MQ 6.2.0 Fabric container to version 6.2.1, proceed as follows:
  1. Make a full backup of your JBoss A-MQ 6.2.0 installation before attempting to apply the patch.
  2. Install the patch management enablement pack for 6.2.0, patch-management-for-amq-620-6.2.1.redhat-084.zip, on top of your 6.2.0 installation. Use an archive utility to extract the contents on top of the existing 6.2.0 installation.
    The patch management enablement pack contains the following files: 
    patches/jboss-a-mq-6.2.0.redhat-133-baseline.zip
system/io/fabric8/patch/patch-commands/1.2.0.redhat-621084/patch-commands-1.2.0.redhat-621084.jar
system/io/fabric8/patch/patch-core/1.2.0.redhat-621084/patch-core-1.2.0.redhat-621084.jar
system/io/fabric8/patch/patch-features/1.2.0.redhat-621084/patch-features-1.2.0.redhat-621084-features.xml
system/io/fabric8/patch/patch-management/1.2.0.redhat-621084/patch-management-1.2.0.redhat-621084.jar
    Note
    It does not matter whether the container is running or not when you extract these files.
  3. Start the container, if it is not already running.
  4. Shut down all of the child containers in the fabric using the container-stop command: 
    fabric:container-stop ChildContainerList
  5. Create a new version for the updated patch mechanism, using the fabric:version-create command: 
    JBossFuse:karaf@root> fabric:version-create 1.0.1
Created version: 1.0.1 as copy of: 1.0
    Important
    The version name must be a pure numeric string, such as 1.0.1, 1.1, 2.1, or 2.2. You cannot incorporate alphabetic characters in the version name (such as 1.0.patch).
  6. Add the new patch feature repository to version 1.0.1 of the default profile, as follows: 
    fabric:profile-edit --repository mvn:io.fabric8.patch/patch-features/1.2.0.redhat-621084/xml/features default 1.0.1
  7. Add the patch and patch-core features to version 1.0.1 of the default profile, as follows: 
    fabric:profile-edit --feature patch --feature patch-core default 1.0.1
  8. Upgrade the root container to version 1.0.1, as follows: 
    fabric:container-upgrade 1.0.1 root
    The effect of this upgrade is to replace the old patch commands by the new patch commands in the current 6.2.0 Fabric container, thereby bootstrapping the new patch mechanism (which is needed to install the 6.2.1 patch).
  9. Wait until the current container is successfully re-provisioned to version 1.0.1 before proceeding to the next phase of the patch installation. You can monitor the provision status of the current container by entering the following console command: 
    watch container-list
    When the [provision status] changes to success, you can proceed with the next step.
  10. Add the 6.2.1 patch to the container's environment using the patch:add command (remembering to customize the path to the patch file), as follows: 
    JBossA-MQ:karaf@root> patch:add file:///path/to/jboss-a-mq-6.2.1.redhat-084.zip
[name]                      [installed] [description]              
jboss-a-mq-6.2.1.redhat-084 false       jboss-a-mq-6.2.1.redhat-084
    Note
    In this case, the patch file is the full distribution of JBoss A-MQ 6.2.1. Under the new patching mechanism, the full distribution file has a dual purpose: you can extract the archive directly, to create a fresh 6.2.1 distribution; or you can add the file as a patch, in order to migrate an existing 6.2.0 installation to 6.2.1.
  11. Create a new version, using the fabric:version-create command: 
    JBossFuse:karaf@root> fabric:version-create 1.1
Created version: 1.1 as copy of: 1.0.1
  12. Apply the patch to the new version, 1.1, using the patch:fabric-install command. Note that in order to run this command you must provide the credentials, Username and Password, of a user with Administrator privileges. For example: 
    patch:fabric-install --username Username --password Password --upload --version 1.1 jboss-a-mq-6.2.1.redhat-084
  13. Synchronize the patch information across the fabric, to ensure that the profile changes in version 1.1 are propagated to all containers in the fabric (particularly remote SSH containers). Enter the following console command: 
    patch:fabric-synchronize
  14. Upgrade each existing container in the fabric using the fabric:container-upgrade command (but leaving the root container, where you installed the patch, until last) along with its respective child containers. For example, to upgrade a container named remote and its child, childOfRemote, enter the following command: 
    fabric:container-upgrade 1.1 remote childOfRemote
    Important
    It is recommended that you initially upgrade only one or two containers to the patched profile version, to ensure that the patch does not introduce any new issues.
    Note
    If the upgraded remote container gives the following error: 
    Provision error:
io.fabric8.common.util.MultiException: Error restarting bundles        at
...
Caused by: org.eclipse.jgit.api.errors.JGitInternalException: Invalid ref name: baseline-ssh-fabric8-1.2.0.redhat-133
...
    This implies that you omitted to follow the steps required to prepare for upgrading an SSH container—see the section called “Preparing for a Fabric SSH container upgrade”.
  15. Keep checking the provision status of the container you are upgrading until the status appears as requires full restart. Enter the fabric:container-list command to check the status, as follows: 
    fabric:container-list
    Note
    After the target container has been upgraded to the patch version, the target container requires a full restart. The restart cannot be performed automatically by the patching mechanism, because the auto-restart capability of the patching mechanism will not become available until after the restart.
    Important
    Do not attempt to restart the container you are upgrading until the status appears as requires full restart.
  16. Use one of the standard mechanisms to stop and restart the container manually. In some cases, it will be possible to do this using Fabric commands from the console of the root container.
    For example, you could stop the remote container as follows: 
    fabric:container-stop remote
    And restart the remote container as follows: 
    fabric:container-start remote
  17. Wait until the provision status of the container you are upgrading appears as success and then start up its child containers (if any). For example, to restart the childOfRemote container: 
    fabric:container-start childOfRemote
  18. Upgrade the root container last (that is, the container that you originally installed the patch on) and its children (if any). For example, to upgrade the root container, root, and its child, childOfRoot, enter the following command: 
    fabric:container-upgrade 1.1 root childOfRoot
  19. Keep checking the provision status of the root container until the status appears as requires full restart. Enter the fabric:container-list command to check the status, as follows: 
    fabric:container-list
    Important
    Do not attempt to restart the root container until the status appears as requires full restart.
  20. The root container must also be restarted manually. Shut it down using the shutdown console command, as follows: 
    JBossFuse:karaf@root> shutdown
Confirm: shutdown instance root (yes/no): yes
    Restart the container manually, as follows: 
    ./bin/amq
    Tip
    If you were invoking the scripts from within the InstallDir/bin directory, you might find that the bin/ directory appears to be empty after the container shuts down. This is because the contents of this directory were re-written by the patch. To see the scripts again, simply re-enter the bin/ directory, for example: cd ..;cd bin.
  21. Wait until the provision status of the root container appears as success and then start up its child containers (if any). For example, to restart the childOfRoot container: 
    fabric:container-start childOfRoot
  22. Now set the default profile version to 1.1 (the version that has the 6.2.1 patch applied): 
    fabric:version-set-default 1.1
    This ensures that when you create new containers from now on, those containers will use the version 1.1 profiles by default (otherwise you would have to specify version 1.1 explicitly in the container create command).
  23. The JBoss A-MQ 6.2.1 rollup patch over-writes the properties from the org.ops4j.pax.logging persistent ID (PID) in the karaf profile (in order to fix a security issue). If you previously made any customizations to this logging PID, they will be over-written. If this is the case, edit the karaf profile to re-apply your changes—for example, by invoking the built-in profile text editor in the Karaf console, as follows: 
    profile-edit --pid org.ops4j.pax.logging karaf 1.1

Rolling back the 6.2.1 patch in a Fabric container

It is not possible to roll back the 6.2.1 patch in a Fabric container. Specifically, if you applied the 6.2.1 patch as described here, then rolling back from profile version 1.1 to version 1.0.1 (using the fabric:container-rollback command) is guaranteed to fail; and rolling back from profile version 1.1 to version 1.0 is also guaranteed to fail.
Warning
Rolling back the patch level from version 6.2.1 to 6.2.0 is not supported in JBoss A-MQ Fabric. This is a special case, because the version 6.2.0 Fabric agent does not support the new patching mechanism.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.