If the keystone user source is immutable, like an LDAP active directory
implementation, the below tempest test cases should able to run with users from configuration or accounts.yaml
tempest.api.identity.admin.v3.test_users.UsersV3TestJSON.test_list_user_projects
tempest.api.identity.admin.v3.test_users.UsersV3TestJSON.test_get_user
tempest.api.identity.admin.v3.test_roles.RolesV3TestJSON.test_grant_list_revoke_role_to_user_on_project
tempest.api.identity.admin.v3.test_roles.RolesV3TestJSON.test_grant_list_revoke_role_to_user_on_domain
tempest.api.identity.admin.v3.test_roles.RolesV3TestJSON.test_grant_list_revoke_role_to_group_on_project
tempest.api.identity.admin.v3.test_roles.RolesV3TestJSON.test_assignments_for_implied_roles_create_delete
tempest.api.identity.admin.v3.test_roles.RolesV3TestJSON.test_assignments_for_domain_roles
tempest.api.identity.admin.v3.test_projects.ProjectsTestJSON.test_associate_user_to_project
tempest.api.identity.admin.v3.test_inherits.InheritsV3TestJSON.test_inherit_assign_list_revoke_user_roles_on_project_tree
tempest.api.identity.admin.v3.test_inherits.InheritsV3TestJSON.test_inherit_assign_list_revoke_user_roles_on_domain
tempest.api.identity.admin.v3.test_inherits.InheritsV3TestJSON.test_inherit_assign_list_check_revoke_roles_on_domains_user
tempest.api.identity.admin.v3.test_inherits.InheritsV3TestJSON.test_inherit_assign_check_revoke_roles_on_projects_user
tempest.api.identity.admin.v3.test_groups.GroupsV3TestJSON.test_list_user_groups
tempest.api.identity.admin.v3.test_groups.GroupsV3TestJSON.test_group_users_add_list_delete
Is it throwing any traceback? Could you please provide some steps on how to reproduce the issue?