Changes

Prometheus/Node exporter support can now be configured (port, enabled/disabled) (CLOUD-3306 and CLOUD-3307)

Fixed

• Fixed application compatibility with S3 v2 and v4 signature methods

• Improved startup handling when storage nodes are initially offline

Known Issues

These are known operational limitations that exist for Gateway 7.4.

• Missing [scsp] allowSwarmAdminIP setting causes startup failure – Verify the setting [scsp] allowSwarmAdminIP exists in gateway.cfg (even if the value is blank) for Content Gateway 7.4. Content Gateway does not start if the setting is not present. Add the following configuration entry to gateway.cfg to mitigate the risk. (CLOUD-3325)

Workaround for Gateway 7.4 startup failure – gateway.cfg

Upgrade Impacts

See Upgrading Gateway to upgrade from a version of Gateway 6. See Upgrading from Gateway 5.x if migrating from Elasticsearch 2.3.3 and Gateway 5.

Address the upgrade impacts for this and each prior version since the currently running version:

See Content Gateway 6 Release Notes for impacts from prior releases.

Watch Items and Issues

These are known operational limitations that exist for Gateway.

• Traffic to the Gateway is blocked unless action is taken to disable IPTABLES or to enable inbound traffic to the front-end protocol port(s) when using the default RHEL/CentOS configuration of IPTABLES.

• Gateway is not compatible with Linux PAM modules that depend upon interactive validation operations such as OTP or biometric scanners.

See Content Gateway 6 Release Notes for known issues from prior releases that are still applicable, apart from those appearing above as Fixed.