4.52.02.02 - Edge for Private Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

On April 14, 2025, we released a new version of Apigee Edge for Private Cloud.

Update procedure

This section describes how to install this release if you are updating from the previous release of Edge for Private Cloud. If you need to update from an earlier release, see Applying Multiple Patch Versions.

Updating this release will update the components listed below:

edge-gateway-4.52.02-0.0.60271.noarch.rpm
edge-management-server-4.52.02-0.0.60271.noarch.rpm
edge-message-processor-4.52.02-0.0.60271.noarch.rpm
edge-postgres-server-4.52.02-0.0.60271.noarch.rpm
edge-qpid-server-4.52.02-0.0.60271.noarch.rpm
edge-router-4.52.02-0.0.60271.noarch.rpm
apigee-cassandra-3.11.16-0.0.2588.noarch.rpm

You can check the RPM versions currently installed to see if they need to be updated by entering:

apigee-all version

To update your installation, perform the following procedure on the Edge nodes:

On all Edge nodes:
1. Clean the Yum repositories:
```
sudo yum clean all
```
2. Download the latest Edge 4.52.02 bootstrap_4.52.02.sh file to /tmp/bootstrap_4.52.02.sh:
```
curl https://software.apigee.com/bootstrap_4.52.02.sh -o /tmp/bootstrap_4.52.02.sh
```
3. Install the Edge 4.52.02 apigee-service utility and dependencies:
```
sudo bash /tmp/bootstrap_4.52.02.sh apigeeuser=uName apigeepassword=pWord
```
  Where uName and pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.
4. Use the source command to execute the apigee-service.sh script:
```
source /etc/profile.d/apigee-service.sh
```
5. Update the apigee-setup utility:
```
apigee-service apigee-setup update
```

On all Cassandra nodes, execute the update.sh script:

/opt/apigee/apigee-setup/bin/update.sh -c cs -f configFile

On all Edge nodes, execute the update.sh script for the edge process (including monetization):
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```

Bug fixes

This section lists the Private Cloud bugs that were fixed in this release.

Issue ID	Description
408438012	Fixes a bug in the Server Registration API that causes deployment failures when Cassandra and RMP nodes are colocated.
405870312	Fixes a bug where `SetOauthV2Info` returns a datastore error if the access token is missing.
395098165	Improved the synchronization delay in Cassandra's authentication scripts to ensure proper role manager initialization, preventing premature timeouts.
408713297	Improved performance of the Server Registration API.

Security issues fixed

No new security issues have been added in this release.

Changes to supported software

No support for new software has been included in this release.

Deprecations and retirements

There are no new deprecations or retirements in this release.

New features

There are no new features in this release.

Known issues

See Known issues with Edge for Private Cloud for a complete list of known issues.

Applying multiple patch versions

This section describes how to apply multiple patch versions, in case you are updating from a version of Edge for Private Cloud that is earlier than the previous patch release version.

Each patch release contains updates to specific components of Edge for Private Cloud, such as edge-management-server. To apply multiple patch versions, you need to update each Edge component that was included in a patch release later than your currently installed version. You can find these components by looking at the Edge for Private Cloud release notes for all versions later than your current version, and checking the list of RPMs for those releases. See Apigee Release Notes for links to all Edge for Private Cloud release notes.

Note: You only need to update each component once, by installing the RPM for the latest version of the component included in the patch releases. Follow the instructions in the release notes for that version to update the component.

Note: Upgrading a component automatically installs the latest patch version of a component. If you want to upgrade to a patch version that is not the latest, you need to maintain your own tarball copy of Apigee's repo using Apigee mirror, and use this mirror for Apigee installations. For more information, refer to Using a local Edge repository to maintain your Edge version.