The bugs that were fixed in the 10.9.1 release of ArcGIS Enterprise on Kubernetes and subsequent updates are described below.
10.9.1 Log4j Update
The list of issues addressed describes bugs that were reported to Esri Technical Support and fixed in the ArcGIS Enterprise 10.9.1 on Kubernetes Log4j Update. The version tag for this release is 10.9.1.1611.
Update Log4j to address security vulnerabilities.
10.9.1 Help Language Pack Update
The list of issues addressed describes bugs that were reported to Esri Technical Support and fixed in the ArcGIS Enterprise 10.9.1 on Kubernetes Help Language Pack Update. The version tag for this release is 10.9.1.1610.
Provide final documentation for all supported languages in ArcGIS Enterprise 10.9.1 on Kubernetes.
10.9.1 Software Release
The list of issues addressed describes bugs that were reported to Esri Technical Support and fixed in the ArcGIS Enterprise 10.9.1 on Kubernetes software release. The version tag for this release is 10.9.1.1599.
The 10.9 backup and restore documentation describing how to configure storage using the ArcGIS Enterprise Administrator API is missing closing curly brackets in both JSON examples.
When specifying a nonexistent TLS secret in the deploy.properties file, the deployment continues and completes without validation or error.
The organization fails to configure when a TLS certificate with a PKCS1-formatted private key is specified during deployment.
The ArcGIS REST Services Directory requires a login to view services that have been shared with everyone.
When ArcGIS Enterprise has been configured with a forward proxy, the organization's print service fails to print.
If a storage class name is not specified when using the setup wizard to create an organization, the organization fails to configure.
When assigning ArcGIS Pro or other add-on licenses from the organization's licenses tab, the member names are not returned.
After importing an updated server license, the system-managed relational data stores are not updated with the new license expiration date.
The documentation contains an erroneous description and JSON example for the Overview API's Update operation.
The ArcGIS Enterprise Administrator API pod is unable to start when the primary relational data store service is inaccessible during startup.
After running the CleanGPJobs task, some geoprocessing job related data items remain.
When an attempt to register a user-managed data store fails, a misleading error message is returned.
The View In ArcGIS Online Map Viewer link from ArcGIS REST Services Directory is incorrectly concatenated and fails to render the map.
After successfully creating an organization, several severe log messages are returned and indicate a server output directory does not exist.
After updating administrative credentials for the metrics viewer app using ArcGIS Enterprise Administrator API, the new credentials are not stored and cannot be used to sign in.
Provide finer-grained warning messages to indicate whether an error occurred while creating an organization.
If a request is made to a GIS service endpoint while it is publishing or starting, the request will fail.
When system and utility services are running, several INFO level messages are logged unnecessarily and cause the logs to fill up.
The apply edits operation fails for service- or layer-level edits when async=true.
While restoring a backup, the ingress service is also re-created, causing a mismatch in the DNS configuration.
Additional issues have been addressed in ArcGIS Enterprise 10.9.1 on Windows and Linux. Many of these also apply to ArcGIS Enterprise on Kubernetes, such as those pertaining to ArcGIS Server or ArcGIS Enterprise portal. See the issues addressed list for details.