4.18.05.07 - Edge for Private Cloud release notes

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

On June 5, 2020, we released a new version of Apigee Edge for Private Cloud.

Update procedure

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

  1. On all Edge nodes:

    1. Clean the Yum repos:
      sudo yum clean all
    2. Download the latest Edge 4.18.05 bootstrap_4.18.05.sh file to /tmp/bootstrap_4.18.05.sh:
      curl https://software.apigee.com/bootstrap_4.18.05.sh -o /tmp/bootstrap_4.18.05.sh
    3. Install the Edge 4.18.05 apigee-service utility and dependencies:
      sudo bash /tmp/bootstrap_4.18.05.sh apigeeuser=uName apigeepassword=pWord

      Where uName:pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.

    4. Update the apigee-setup utility:
      sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
    5. Use the source command to execute the apigee-service.sh script:
      source /etc/profile.d/apigee-service.sh
  2. Run the update.sh script for OpenLDAP on all nodes. On each node, execute the following command:
    /opt/apigee/apigee-setup/bin/update.sh -c ldap -f configFile

    Where configFile specifies the silent configuration file that you used to install Apigee Edge for Private Cloud.

  3. Run the update.sh script for Edge on all nodes. On each node, execute the following command:
    /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

    Where configFile specifies the configuration file that you used to install Apigee Edge for Private Cloud.

Supported software

No changes.

Deprecations and retirements

No changes.

Bugs fixed

The following table lists the bugs fixed in this release:

Issue ID Description
155595660

Timezone format

The values used for the sss and SSS tokens in the timezone format set by the conf_system_apigee.syslogger.dateFormat property were not correct.

148486685

Indirect bind OpenLDAP replication and SSO interoperability

With indirect binding, the OpenLDAP service was not searching the user object when replication was enabled (there was more than one OpenLDAP instance).

120799182

OpenLDAP upgrade

The process for upgrading OpenLDAP in a multi-datacenter environment resulted in a corrupted state.

76087166

KVMs in multi-data center environments

The Management Server was randomly connecting to any of the datacenters if an organization spanned multiple datacenters (for example, dc-1, dc-2). This affected connections to the Cassandra nodes in the local data center for key management and Key Value Map (KVM) operations.