Hotfixes

What are Hotfixes?

Hotfixes are an immediate fix for a customer reported incident and will always be applied on an update level. Hotfixes are in the form of a .zip file that needs to be applied on top of the product pack using the update client tool. Further, A hotfix is particular to a customer reported issue, and an update level.

Hotfixes are best-suited if you are:
1. Experiencing a sudden issues, after a long error-free spell in your production environment.
2. Have tested a certain update level thoroughly in a QA Environment and just before concluding testing you have found some test cases are failing.
3. Having a single issue to be addressed and needs to be push the production environment soon. Reporting an issue and receiving a hotfix saves you time and trouble.

How to apply hotfix(es)?

As you already know hotfixes for an important fix is received as a zip file. The zip file can be applied to your environment as shown as here

How to create a Docker image with Hotfixes?

Creating a hotfix applied Docker image is simple. Follow the steps given below to seamlessly get updates and hotfixes to your containerized environment.
  1. Create an updated product pack to the corresponding update level.
  2. Download and copy the hotfix file to the relevant machine (e.g., Desktop or Server)
  3. Apply the hotfix command to install the hotfix for the update level.
  4. Then run the 'create-docker' command to create a Docker image with hotfixes. Follow    instructions given in the update commands page
  5. Thereafter, add the created Docker image to your private Docker registry.
  6. Rollout the newly created Docker image to Staging environment and test thoroughly.
  7. If all compliance test are passing, follow Step 5 in other environments including the    Production environment.

How move hotfixes to the latest update level in a containerized environment?

Once the issue has been addressed in an update level, we recommend you to move to the update level that includes the fix or latest update level. This can be done by retrieving the docker image from the WSO2 private Docker registry with the right version tag.

Steps to follow if you are moving from hotfixes to the latest update level on your product pack

Hotfixes are temporary fixes provided to address critical issue(s) in the production environment. Once the issue has been addressed in an update level, we recommend you to revert the hotfix(es) and move to the latest update level.

This can be done using the following steps:

  1. Run the following command from the bin folder (<product-home>/bin) to check the current state: This command will list all the hotfix(es) that has been applied to a particular product pack.

    ./wso2update_<os> current-state

  2. Run the following command that will remove the last applied hotfix. If there are multiple hotfixes applied, repeat the command for each of them.

    ./wso2update_<os> revert-hotfix

  3. Then run the current-state command again to verify that all hotfixes are removed.

Note

Make sure all the hotfixes applied to the pack are reverted before you proceed to the next step.


4. Lastly, run the update tool to update to the latest update level containing the fixes corresponding to all the hotfixes.
./wso2update_<os>

Refer the webinar link to learn more on the reverting hotfixes.

Top