Open vvanouytsel opened 4 months ago
Files identified in the description:
If these files are incorrect, please update the component name
section of the description or use the !component
bot command.
cc @adamgoossens @eikef @mattock @ndclt click here for bot help
I encounter the same issue. And it works with keycloak 22.X. The issue trigger on keycloak 23.X and 24.X
Looks like it is related to a change in keycloak sub group representation since KC 23 : https://www.keycloak.org/docs/23.0.0/upgrading/index.html#grouprepresentation-changes
ansible module should now call expliciterly the children API to get information, as stated in this report: https://github.com/keycloak/keycloak/issues/25053#issuecomment-1892193969
cc @thomasbach-dev click here for bot help
Summary
The example below is shown in the documentation but is not working. The subgroup gets created but the error message is still thrown.
The full play I used to test this:
The result of the failing task using
-vvv
:If you run it again it will fail because the subgroup is already created. So the interesting part is that the subgroup does get created, but during creation it throws an error.
Issue Type
Bug Report
Component Name
keycloak_group
Ansible Version
Community.general Version
Configuration
OS / Environment
NAME="AlmaLinux" VERSION="9.3 (Shamrock Pampas Cat)" ID="almalinux" ID_LIKE="rhel centos fedora" VERSION_ID="9.3" PLATFORM_ID="platform:el9" PRETTY_NAME="AlmaLinux 9.3 (Shamrock Pampas Cat)" ANSI_COLOR="0;34" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:almalinux:almalinux:9::baseos" HOME_URL="https://almalinux.org/" DOCUMENTATION_URL="https://wiki.almalinux.org/" BUG_REPORT_URL="https://bugs.almalinux.org/"
ALMALINUX_MANTISBT_PROJECT="AlmaLinux-9" ALMALINUX_MANTISBT_PROJECT_VERSION="9.3" REDHAT_SUPPORT_PRODUCT="AlmaLinux" REDHAT_SUPPORT_PRODUCT_VERSION="9.3"
Steps to Reproduce
Expected Results
I expect the subgroup to be created without any errors. I also expect the next time that the play runs, it does not fail with the message that the subgroup already exists. I would expect the module to be idempotent.
Actual Results
The first time, when the subgroup does not yet exist:
The second time when the subgroup exists (even though the task fails):
Code of Conduct