Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Changes
The retention duration for S3 object locking may be constrained by the storage administrator at the bucket and domain level. (CLOUD-3932)
Gateway 8.0.2 produces many harmless error logs like:
Code Block XmlUtil: Document root element "ObjectLockConfiguration", must match DOCTYPE root "null". XmlUtil: Document is invalid: no grammar found.
These can be stopped by appending XmlUtil these three lines to /etc/caringo/cloudgateway/logging.yaml. This will be fixed in the upcoming release.
Code Block language yaml ## Workaround noisy 8.0.2 log (CLOUD-3765) - name: com.caringo.gateway.util.XmlUtil level: fatal
Upgrade Impacts
SeeĀ Upgrading Gateway to upgrade from a version of Gateway 6 or 7. SeeĀ Upgrading from Gateway 5.x, if migrating from Elasticsearch 2.3.3 and Gateway 5.
...
Excerpt | ||
---|---|---|
| ||
Impacts for 8.0.2
|
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
Insert excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
|
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 not compatible with Linux PAM modules that depend on 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 versionsv8.0 and later versions fail to generate video clips. (CLOUD-35164082)
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.