4.16.01.06 - Edge for Private Cloud release notes

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

On Wednesday, October 26, 2016, we released a new version of Apigee Edge for Private Cloud.

Update procedure

To update your installation, perform the following procedure:

On all Edge nodes, clean Yum repos:
> sudo yum clean all
On all Edge nodes, update apigee-setup:
> /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
On all Edge nodes, update edge-gateway:
>/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile

where configFile specifies the config file you used to install Edge.
On all Edge UI nodes, update edge-ui:
>/opt/apigee/apigee-setup/bin/update.sh -c ui -f configFile

This update includes the fix for EdgeUI-675. After you perform this update, you can configure the Edge UI to allow OpenAPI specs to define requests to private IP addresses as described below.
If you have installed Edge Monetization services only, apply the patch for DEVRT-3098:
> /opt/apigee/apigee-service/bin/apigee-service edge-mint-management-server add-missing-notification-templates -f configFile

where configFile specifies the config file you used to install Edge.

Bugs fixed

The following bugs are fixed in this release.

Note: The build number in the table specifies the earliest version of the component that contains the fix. Use that build number to determine if you already have the fix installed, or if you need to perform an update. The apigee-service utility displays the build number of the currently installed component:

/opt/apigee/apigee-service/bin/apigee-service comp version

where comp is the name of the component without the build number extension. For example:

/opt/apigee/apigee-service/bin/apigee-service apigee-setup version

or get the build number of all components:

/opt/apigee/apigee-service/bin/apigee-all version

Issue ID	Description	Build number
APIRT-1144	XML to JSON policy enhancements The XML to JSON policy has been enhanced with the following capabilities. You can configure the policy to: Treat some XML elements as arrays during conversion, which puts the values in square brackets '[ ]' in the JSON document. Strip or eliminate levels of the XML document hierarchy in the final JSON document. For more information, see XML to JSON policy	edge-gateway-4.16.01-0.0.785
APIRT-3389	Error uploading Node.js payloads over 25KB You can now upload Node.js payloads larger than 25KB.	edge-gateway-4.16.01-0.0.785
DEVRT-3098	Error encountered when setting up Monetization notification templates using the UI An error is raised when setting up Monetization notification templates using the UI, as described in Set up notifications using notification templates.	edge-ui-4.16.01-0.0.3741
EDGEUI-675	Allow OpenAPI specs to access private IP Addresses By default, Edge prevents OpenAPI specs from referencing private IP addresses. You can now enable access to private IP addresses: Open the ui.properties file in an editor. If the file does not exist, create it. > vi /<inst_root>/apigee/customer/application/ui.properties Set the following property to true: conf_apigee-base_apigee.feature.enableopenapiforinternaladdresses="true" Save your changes to ui.properties. Restart the Edge UI: > /<inst_root>/apigee/apigee-service/bin/apigee-service edge-ui restart	edge-ui-4.16.01-0.0.3741

Known issues

This release has the following known issues.

Issue ID	Description
APIRT-2978	Router fails to start Nginx or Router fails to start If the Edge Router fails to start Nginx or fails to start at all, as shown in the /opt/apigee/var/log/edge-router/logs/system.log file, then delete all files in the /opt/nginx/conf.d directory, and restart the router: > rm -f /opt/nginx/conf.d/* > /opt/apigee/apigee-service/bin/apigee-service edge-router restart
PRC-1118	Error when running "apigee-service apigee-postgresql pg-data-purge" command If you run the "apigee-service apigee-postgresql pg-data-purge" command and see an error in the form: ERROR: must be owner of relation Edit /opt/apigee/apigee-postgresql-4.16.05-0.0.894/lib/actions/pg-data-purge and set the following property to 'apigee': POSTGRES_USER=apigee
DOC-1687	Due to a known package dependency conflict, the Katello agent used in Satellite Server 6 will not install properly on Apigee Edge hosts running the Qpid daemon.

Issue ID

Description

APIRT-2978

Router fails to start Nginx or Router fails to start

If the Edge Router fails to start Nginx or fails to start at all, as shown in the /opt/apigee/var/log/edge-router/logs/system.log file, then delete all files in the /opt/nginx/conf.d directory, and restart the router:

> rm -f /opt/nginx/conf.d/*
> /opt/apigee/apigee-service/bin/apigee-service edge-router restart

PRC-1118

Error when running "apigee-service apigee-postgresql pg-data-purge" command

If you run the "apigee-service apigee-postgresql pg-data-purge" command and see an error in the form:

ERROR: must be owner of relation

Edit /opt/apigee/apigee-postgresql-4.16.05-0.0.894/lib/actions/pg-data-purge and set the following property to 'apigee':

POSTGRES_USER=apigee

DOC-1687

Due to a known package dependency conflict, the Katello agent used in Satellite Server 6 will not install properly on Apigee Edge hosts running the Qpid daemon.

4.16.01.07

4.16.01.05