Changes

• A new audit log tag showing milliseconds during quota evaluation will now appear on requests potentially impacted by quotas. (CLOUD-4064)

• Nakivo backup software sets the x-amz-meta-owner metadata header via S3, which caused conflicts with the x-owner-meta SCSP metadata header in Gateway versions before 8.2.0. (CLOUD-4069)

• All Gateway servers running with Swarm product or Elasticsearch must be configured with LANG=en_US.UTF-8. If "locale" reports anything except "C.UTF-8" or "en_US.UTF-8", run sudo localectl set-locale LANG=en_US.UTF-8, then reboot. See Rolling Restart of Elasticsearch. (CLOUD-4056)
  Remember to follow the rolling reboot procedure on elasticsearch servers which involves disabling shard allocation:

• When listing caching is enabled, Gateway ensures a minimum of 20 GB free disk space on /var/spool/caringo/cloudgateway at startup, and will fail to start if this condition is not met. (CLOUD-4038)

Upgrade Impacts

See Upgrading Gateway to upgrade to an existing installation. See Upgrading from Gateway 5.x, if you are migrating from Elasticsearch 2.3.3 and Gateway 5.

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

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

See Content Gateway 7 Release Notes and 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 incompatible with Linux PAM modules that depend on interactive validation operations such as OTP or biometric scanners.

• Gateway 8.0.4 and later versions must be restarted after creating a Search Feed to avoid the error: “ResourceUnavailableException: Application resource 'elasticsearch-storage_cluster' is unavailable”. (CLOUD-4003)

• Gateway logs display a warning "Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone". This is harmless and can be avoided by adding "xpack.security.enabled: false" to each Elasticsearch node's /etc/elasticsearch/elasticsearch.yml and doing a rolling restart Rolling Restart of Elasticsearch. (SWAR-10260)

• Gateway v8.0 and later versions fail to generate video clips. (CLOUD-4082)

• Gateway 8.1.0 may report an incorrect IsTruncated status in rare cases where ?max-keys=0. This will be fixed in the future release.

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