« Third-party software dependencies Documentation Stubs »
Elastic Docs ›Elastic Cloud Enterprise Reference [3.7] ›About this product

Limitations and known problems

edit

Limitations and known problems

edit

The following limitations and known problems apply to the 3.7.3 release of ECE, or to earlier releases as noted.

For troubleshooting help, you can also refer to the list of Common issues.

Installation and configuration

edit
  • When you install Elastic Cloud Enterprise on a new host and assign it the allocator role from the command line with the --roles "allocator" parameter during installation, new deployments might not get created on the allocator. To resolve this issue, check Allocators Are Not Being Used.
  • Some change management tools that auto-reload firewall rules can cause networking issues. Specifically, Docker networking can fail on new containers after restarting the iptables service. To avoid networking failures, disable the automatic reloading of firewall rules.
  • When you use OverlayFS with Kernel-LT 4.4.156 and later, there is a known regression that prevents Elastic Cloud Enterprise from completing the installation. This regression is fixed with Kernel-LT 4.9.
  • If you install ECE on AWS, you likely need to modify the cluster endpoint, as the public hostname resolves to a different IP address externally than it does internally on the cluster.
  • ECE is unable to support VMotion functionality in VMWare. To use ECE, you must disable VMotion.
  • When you use virtualization resources, make sure that you avoid resource overallocation.

Security

edit

  • Changing the generated password for the admin user on the administration console deployment that backs the Cloud UI is not supported. This is the admin user on the admin-console-elasticsearch deployment that gets created during the ECE installation.

    Do not change the generated password for the admin user on the administration console deployment or you risk losing administrative access to your installation.

  • When configuring Elastic Cloud Enterprise role-based access control:

    • Trying to use an invalid SAML provider can cause the security deployment to bootloop. The deployment falls back to the previous configuration, but if there are any issues between the UI and the actual configuration, remove or update the SAML provider profile. If the problem persists, review the deployment activity and logs.
    • Regarding the principal user property, although the SAML specification does not have many restrictions on the type of value that is mapped, ECE requires that the mapped value is also a valid Elasticsearch native realm identifier. Specifically, this means the mapped identifier should not contain any commas or slashes, and should be otherwise URL friendly.
    • PEM and PKCS11 formatted certificates are not supported.
  • In versions from 2.6 to 2.10 included, some or all platform certificates are generated with a 398-day expiration. Installations that ran on these versions, even temporarily, must have their certificates rotated manually before expiry. For details, check our KB article.
  • The administration console may become unavailable when the route server certificate expires. Until the rotation of this certificate gets automated, you need to perform the rotation manually if you encounter this issue. For details, check our KB article.

Some additional limitations apply when securing your installation. To learn more, check Secure Elastic Cloud Enterprise.

Deployments

edit
  • Pending plan changes for your deployment in the Cloud UI that exceed the available capacity will fail as expected, but might then require you to manually recover from the failure. (To recover, locate the details for the plan attempt and copy the diff; manually edit the diff to revert to the original plan and apply the modified plan into the Advanced cluster configuration panel.)
  • ECE has a maximum limit of 320 seconds, so we recommend optimizing long-running queries in Elasticsearch.

Deployment templates

edit
  • In ECE 2.13, a known issue can prevent custom deployment templates from being created through the UI, when selecting instance configurations different from the default ones. This results in an error related to autoscaling displayed in the UI when you try to create the template. If you are affected by this issue, you can contact support@elastic.co.

Upgrading

edit
  • Due to a known Elastic Agent bug, Elastic Agent or Integrations Server components running on version 8.11.0 will not boot up within an Elastic Cloud Enterprise deployment. The issue affects Elastic Cloud Enterprise installations that are deployed with a Linux UID other than 1000.

We recommend upgrading your deployments and components to version 8.11.1 or above to fix this issue.

  • A known issue can prevent direct rolling upgrades from Elasticsearch version 5.6.10 to version 6.3.0. As a workaround, we have removed version 6.3.0 from the Cloud UI for new cluster deployments and for upgrading existing ones. If you are affected by this issue, check Rolling upgrades from 5.6.x to 6.3.0 fails with "java.lang.IllegalStateException: commit doesn’t contain history uuid" in our Elastic Support Portal. If these steps do not work or you do not have access to the Support Portal, you can contact support@elastic.co.
  • When upgrading to 2.4.0, make sure that nothing listens on your proxy node over port 9000. If a Minio repository runs on the same ECE node, you’ll need to change the default listening port. If there is a port conflict, proxy fails and won’t boot.
  • Starting with ECE version 2.6.0, deployment upgrades initiated from the UI can fail if there is no healthy instance of Kibana available. As a workaround, you can perform an advanced edit on the cluster to upgrade the cluster version. In the cluster configuration, each occurrence of elasticsearch.version can be updated to the version that you choose. For details, check Advanced cluster configuration.
  • When upgrading to ECE version 2.7.0 the automatic upgrade of the admin-console-elasticsearch cluster may fail, particularly on older installations of ECE that started with a 5.x cluster. If this happens, it is safe to leave the cluster at the latest 6.x Elasticsearch version until the automatic upgrade is fixed in the next version of ECE. Note that the logging-and-metrics cluster should also remain on 6.x, only the security cluster should be upgraded to the latest 7.x Elasticsearch version using the dedicated API.
  • When upgrading from version 2.9.x (2.9.0, 2.9.1, 2.9.2) to a version between 2.10.0 and 2.11.0, you might get an error that indicates deployment aliases cannot be set in the console. As a workaround, you can fix it using the dedicated API by setting the value of config_option_id to enable-deployment-alias and the value of request body to { "value": "false" }.

Integrations Server

edit

A bug in Elastic Stack versions 8.1 and later may lead to a full disk for Elastic APM users with tail-based sampling enabled. A fix has been merged and will be released in a future version.

Kibana

edit

Due to a bug in ECE, audit logging for Kibana must be enabled using the flattened format of the key/setting: xpack.security.audit.enabled: true. Using a nested yaml format will not take effect.

« Third-party software dependencies Documentation Stubs »