Changes

• Fixed "Failed to load collection contents" error and now, unnamed, untenanted streams are visible in the Content UI. (CLOUD-3658)

• Fixed date conflict in Lifepoint and X-Object-Lock-Meta-Retain-Until-Date header and object deletion is now allowed for mismatched dates. Earlier, this affected some Veeam backup configurations. (CLOUD-3692)

• An object or version-specific delete with governance bypass header and permission would fail to check if the version was locked with compliance or legal hold permission. This is possible with user permission. (CLOUD-3693)

• The S3 location query (AKA regions) no longer returns the Swarm cluster name as the location. Rather, a default location may be set in the [s3]region config item. It may also be specified in an S3 bucket creation request. Neither set it default nor specified at creation; the default is empty that clients interpret as "us-east-1".

  To prevent backup failures, Veritas NetBackup users must change their currently configured bucket location from the Swarm cluster name to the default “us-east-1” or configure [s3] region = <cluster.name> in gateway.cfg and restart. (CLOUD-3666)

• Fixed a bug in which locking an object with URI-reserved characters (such as an asterisk or parenthesis) in the name would result in a 500 response “Requested object was not found, per overlay index lookup”. (CLOUD-3685)

• Upgrade log4j library to 2.19 to avoid a security vulnerability because log4j 2.16 still had some security vulnerabilities. (CLOUD-3682)

• Metadata values containing (Non-ASCII) ISO-8859-1 characters were converted to UTF-8 bytes when written via Gateway 5.3 through 7.10.1. Two streams (GET or HEAD) with ISO-8859-1 metadata resulted in a 500 error “MalformedInputException” via Gateway <= 7.10.1, this exception has been fixed and ISO-8859-1 metadata is preserved with Gateway 7.10.2.

• Fixed a bug that caused erroneous 500 errors if the optional ‘indexerHosts’ line was commented out in the gateway configuration. (CLOUD-3614)

• If [folder_listings]usePaths is set to true, without Swarm Storage setting search.enableDelimiterPaths being set to true, Gateway will ignore the setting and log an error indicating the problem. (CLOUD-3631)

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.

Starting from Gateway 7.8, Elasticsearch 6.8.6 is no longer supported. Remain on Gateway 7.7 until the rolling upgrade is completed from Elasticsearch 6.8.6 to 7.5.2.

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.

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

• 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.