-
Notifications
You must be signed in to change notification settings - Fork 23.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aci_aaa_user: Setting user password is not idempotent #35544
Labels
aci
Cisco ACI community
affects_2.5
This issue/PR affects Ansible v2.5
bug
This issue/PR relates to a bug.
cisco
Cisco technologies
module
This issue/PR relates to a module.
networking
Network category
support:certified
This issue/PR relates to certified code.
waiting_on_vendor
This issue requires actions by the vendor. Please inquire the vendor's help for any progress.
Comments
Files identified in the description: If these files are inaccurate, please update the |
Issue moved to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
aci
Cisco ACI community
affects_2.5
This issue/PR affects Ansible v2.5
bug
This issue/PR relates to a bug.
cisco
Cisco technologies
module
This issue/PR relates to a module.
networking
Network category
support:certified
This issue/PR relates to certified code.
waiting_on_vendor
This issue requires actions by the vendor. Please inquire the vendor's help for any progress.
ISSUE TYPE
COMPONENT NAME
aci_aaa_user
ANSIBLE VERSION
v2.5
SUMMARY
Due to an inconsistency in the APIC REST API, a task that sets the password of a locally-authenticated user is not idempotent. The APIC will complain with message
Password history check: user dag should not use previous 5 passwords
.This seems to be a bug in the APIC as according to APIC REST API documentation:
The APIC in this case should really be testing whether the provided password is identical to the existing password, before testing it against the password history.
The vendor is notified of this inconsistency.
The text was updated successfully, but these errors were encountered: