Checking for Incompatibilities between Version 24.2.0 and 24.3.0

As a system administrator, you need to check incompatibilities between consecutive versions before upgrading your system.

Important!

Each page lists the possible incompatibilities between two consecutive versions. If you are skipping one or more versions when upgrading, make sure you go through all the relevant pages. For example, if you upgrade from 24.0 to 24.3, you must read the pages for the 24.0 to 24.1, 24.1 to 24.2 and 24.2 to 24.3 pages.

The tables below lists new features that might lead to compatibility issues or should be taken care of when upgrading; they do not list all new features of this AE version. New features are described in full in the Release Highlights and Release Notes.

More information:

To provide a better overview, the tables are categorized by the severity of the issue. There are three different categories:

  • Critical: Issues that must be addressed, otherwise the system will not work
  • Behavior change: Functionality changes in existing features that might have an impact on your system
  • Advisory: Different issues you should be aware of but might not have an impact on your system

The columns display the following information:

  • Topic: Name of the general topic or new feature
  • Changed behavior: What has been changed
  • Possible incompatibilities: Impact the change may have
  • Actions/Countermeasures: What can be done to identify and/or remove possible incompatibilities

This page includes the following:

Automic Automation

Advisory

Topic

Changed Behavior

Possible Incompatibilities

Actions/Countermeasures

General DB change

Note: Information and the checking instructions apply to all versions, between your existing installation and the latest you want to upgrade to, respectively.

 The DB schema/structure has been changed. Custom SQL queries on the AE database might not work after a change in the database schema/structure.
  • Check and adapt relevant SQL/SQLI/SQLJOBS objects accordingly
  • Check and adapt relevant DB queries used in external tools/programs

Automic Automation Kubernetes Edition

Critical

Topic

Changed Behavior

Possible Incompatibilities

Actions/Countermeasures
AAKE memory resources for requests and limits Java processes using -Xmx do not allow power-of-two-based units. Therefore, when defining memory resources allocated to each pod, it is no longer allowed to use Mi and Gi memory values. You must use only decimal unit (M and G) values. The helm upgrade fails with an error message pointing out that the values defined do not match the schema specified. Make sure you use only decimal units when defining the values

Advisory

Topic

Changed Behavior

Possible Incompatibilities

Actions/Countermeasures
System name in values.yaml file

It is no longer possible to deploy AAKE using a default name.

The system name must be set explicitly using the AUTOMIC_GLOBAL_SYSTEM and AUTOMIC_SYSTEM_NAME environment variables

If no system name is defined the Helm installation will fail and AAKE deployment will not start.

Make sure you set the system name before deploying AAKE, for example:

environment:
  AUTOMIC_GLOBAL_SYSTEM: AUTOMIC
  AUTOMIC_SYSTEM_NAME: AUTOMIC
AAKE deployment no longer with CRD (custom resource definition)

New AAKE installations no longer use the CRD (custom resource definition) automic-automation. Instead of it, the automic-automation configuration is held in a config map.

Cluster administrator role is no longer required. You can reduce the rights of AAKE administrators given that they do not require cluster administration roles anymore.