Changes

• Changed the message about SOSAPI being enabled or disabled to print only once during Gateway startup. (CLOUD-3780)

• Preserved object locking headers for greater S3 compatibility when an object lock expires. (CLOUD-3767)

• Fixed bug in which deleted folders would still be included in non-versioned S3 delimiter listings when [folder_listings] usePaths=true. (CLOUD-3772)

Upgrade Impacts

See https://perifery.atlassian.net/wiki/spaces/public/pages/2443817319, to upgrade from a version of Gateway 6. See https://perifery.atlassian.net/wiki/spaces/public/pages/2443817356, 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 https://perifery.atlassian.net/wiki/spaces/public/pages/2443806569 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.

• Gateway SCSP and Portal do not allow a bucket with object locking to be deleted, even if it is empty. It must be deleted by an S3 client e.g. using "rclone purge" to delete all objects and versions. (CLOUD-3516)

See https://perifery.atlassian.net/wiki/spaces/public/pages/2443806569 for known issues from prior releases that are still applicable, apart from those appearing above as Fixed.