Known Issues
This part of the documentation applies both to Omada Identity Cloud and Omada Identity Cloud Private. See the Known issues section of the Omada Identity Cloud documentation.
If there are any issues applicable to Cloud Private specifically, they will be listed on this page.
Installation script fails to upgrade from July 2026 to September 2026
Upgrading directly from the July 2026 release to the September 2026 release with the installation script is currently not supported.
To upgrade an environment on the July 2026 release, first upgrade to the August 2026 release, and then upgrade from August 2026 to September 2026. Environments already on the August 2026 release can upgrade directly to September 2026.
Ansible module deprecation warnings
When running the Ansible phases of the Omada Identity Cloud Private installation script, you may see deprecation warnings in Ansible task output related to imports from ansible.module_utils._text. The to_bytes, to_native, and to_text imports are deprecated as of Ansible 2.24 and will be removed in future releases. These warnings come from the Azure Ansible collection and do not affect task execution with the current pinned Ansible Core version.
Cloud Application Gateway – instance groups displaying the same name
Cloud Private deploys the Linux Cloud Application Gateway to two instance groups, Default and OmadaHosted. Their workers are displayed with the same name in the System Heartbeats section (Setup > Operations Dashboard > System Heartbeats), so users cannot tell the two instance groups apart in the list by name alone. All workers function correctly.
To identify a specific worker, use the Cloud Application Gateway Instances page and match on Service UID rather than on Machine Name.
For more information, see CAG in Cloud Private: architecture overview.
Identities page – error message
An error message may appear on the Identities page indicating an incomplete response from the api/Configuration/EnterpriseServerReportingDashboards endpoint, with missing Tenant Id and Analytics Base Url values. This error message does not affect the functionality of the Identities page or prevent any operations.
Terraform apply fails with a connection reset error
During installation, the Terraform apply can fail while creating an App Service, with an error similar to the following:
Error: creating Linux App Service (Subscription: "<subscription-id>"
Resource Group Name: "<resource-group>"
Site Name: "<site-name>"): performing CreateOrUpdate: Put "https://management.azure.com/...": HTTP response was nil; connection may have been reset
This is a transient Azure error. Re-run the same installer command with --resume appended to continue from the last completed phase.