Mesh and GravityZone integration known issues and workarounds
1. Failed to create tenant – Admin email already exists in Mesh
Description:
Tenant creation fails because the admin email address is already associated with an existing Mesh tenancy. When selecting Create account for a tenant, a message is displayed informing you that the action failed.
Resolution:
Ensure the admin email is not already used for another Mesh tenant.
If the email is already in use, update it to a different email address. You can also create a new user with a unique email and the appropriate permissions in GravityZone.
If the issue persists, contact support for investigation and tenant/user mapping validation.
Note
In certain scenarios, reusing email addresses across Mesh tenants may lead to conflicts that cannot be resolved without backend intervention.
2. Failed to create tenant - Tenant already exists
Description:
The tenant you are trying to create already exists in Mesh.
Resolution:
Verify whether the tenant was previously created.
Avoid retrying creation for the same tenant.
If the tenant cannot be accessed or mapped correctly, contact support and provide details of the existing Mesh tenancy for proper mapping to GravityZone.
3. Failed to create tenant - Admin user does not exist for partner
Description:
This occurs when attempting to create a partner company or tenant without any users defined.
Resolution:
Create the first user in the partner company with administrative rights. Retry tenant creation after the user is available.
4. Distributor access limitations
Description:
Distributors can create tenants, but they can only log in to their own tenancy.
Impact:
Limited visibility and access across managed tenants.
Note
Full distributor access (FaD) is planned for a future update. This is a known limitation, not an error condition.
5. Tenant not visible in GravityZone
Description:
A Mesh tenancy does not appear in GravityZone after the update.
Resolution:
Contact support to validate and complete tenant mapping in GravityZone.
6. Licensing inconsistencies
Description:
License information may appear incorrect, incomplete, or not aligned with the expected setup after provisioning.
Resolution:
Verify the intended license configuration. Contact support to validate and correct license mapping.
Note
This is typically caused by backend mapping or provisioning inconsistencies.
7. GravityZone IdP login method requirement
Description:
Users without the GravityZone IdP login method enabled cannot access the Mesh console.
Symptoms:
The Open Console option is grayed out. A tooltip is displayed on hover, indicating a missing login method.
Resolution:
Ensure the user has the GZ IdP login method enabled.
If the issue persists:
Contact support to verify user configuration and login method assignment.