OAT V4.3.0

Purpose

To better assist users in maintaining OceanBase products, OAT V4.3.0 introduces in-depth inspection capabilities. This feature allows for in-depth inspections of products, components, and tools managed by OAT, with the ability to view and download inspection reports. Additionally, the update includes support for OCP rolling upgrades, enabling OCP to provide read-only services during the upgrade process. OAT V4.3.0 also adds support for upgrading MetaDB V4.x, as well as version rollback for OCP, ODC, and OB Sharding. This allows users to easily roll back to the previous version in case of failed upgrade tasks or issues found during post-upgrade verification. The update further enhances the node management capabilities of odpconsole, supporting node addition, deletion, replacement, and resource specification modification.

Overview

• Release date: 2024.10.28

• Previous version: V4.2.1BP1

• Version: V4.3.0

New features

• Supports in-depth inspection feature, allowing for in-depth inspections of products, components, and tools managed by OAT, with the ability to view and download inspection reports

• Supports OCP rolling upgrades, enabling OCP to provide read-only services during the upgrade process (Version restriction: OCP V4.3.0 and later)

• Supports version rollback for OCP, ODC, and OB Sharding, addressing user concerns about version upgrades

• Supports NLB resource change functionality, including node addition and replacement (single-node NLB does not support node replacement) and resource specification modification

• Supports modification of SQLAuditStore node resource specifications

• Supports resource changes for odpconsole, including node addition, deletion, replacement, and resource specification modification

• Optimized server management feature: added options to specify server purpose and custom installation path; supports setting file system type during disk initialization

• Supports synchronization of product/component time zone with OS

• Supports upgrading MetaDB V4.x

Bug fixes

• Optimized OMS maintenance logic

• Fixed the issue where configured passwordless credentials lose the private key in upgrade scenarios

• Fixed the issue where OCP reported an error when deleted OBDNS/OBLB was synchronized and the corresponding OCP was already deleted

• Fixed the issue where the system parameter OCP credential needed to be updated after renaming the OCP

• Fixed the issue where the ODC container was not deleted when an ODC task was deleted

• Fixed the issue where a kill operation was required when modifying the server's SSH port or using new credentials

• Fixed the issue where the script for installing Docker in an all-in-one package did not handle cgroup v2

• Fixed the issue where exec permission was required in the observer directory for installing MetaDB

• Fixed the issue where the database being customized needed to be backed up during upgrade

• Fixed the issue where the primary zone of the sys tenant of MetaDB V2.2.77 could not be set to random

• Fixed the issue where an error was reported during the initialization of an external server for OAT if the IP address was not that of the local server

Known issues

• The time sorting feature for in-depth inspection history is unavailable

• The SQLAuditStore component is not counted on the Workspace page

• The check box for an ongoing inspection task cannot be selected on the inspection history page

• The server selection box for InfluxDB and SQLAuditStore components on the frontend only allows selection of a single server

• Optimized the details page of the OBSharding component

Considerations

OAT 4.x supports in-place upgrade from OAT 3.2.0 or later. The ecosystem products deployed on earlier versions of OAT or Antman can be migrated to a newly deployed OAT instance using the "Take Over Component" and "Take Over Product" features.

Upgrade guide

Upgrade guide

Support matrix