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_rest: Using status="created" behaves differently than status="deleted" #35050
Labels
aci
Cisco ACI community
affects_2.4
This issue/PR affects Ansible v2.4
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 |
ansibot
added
affects_2.4
This issue/PR affects Ansible v2.4
bug_report
module
This issue/PR relates to a module.
networking
Network category
support:community
This issue/PR relates to code supported by the Ansible community.
labels
Jan 18, 2018
dagwieers
added
the
waiting_on_vendor
This issue requires actions by the vendor. Please inquire the vendor's help for any progress.
label
Jan 31, 2018
I am not able to reproduce this on version 3.0(2k) running on sandboxapicdc.cisco.com. Either the identified problem is more complex, or this is already fixed in a newer release. |
ansibot
added
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
and removed
support:community
This issue/PR relates to code supported by the Ansible community.
labels
Sep 18, 2018
ansibot
added
support:community
This issue/PR relates to code supported by the Ansible community.
and removed
support:core
This issue/PR relates to code supported by the Ansible Engineering Team.
labels
Oct 4, 2018
ansibot
added
support:certified
This issue/PR relates to certified code.
and removed
support:community
This issue/PR relates to code supported by the Ansible community.
labels
Oct 12, 2018
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.4
This issue/PR affects Ansible v2.4
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_rest
ANSIBLE VERSION
v2.4+
SUMMARY
If you use a REST payload with aci_rest using
status="created"
the action is not idempotent. The first time (when the object does not exist) it works (changed=True
), but a subsequent call fails as the APIC returns an HTTP failure.However, if you do the same for removing an object using
status="deleted"
the action is idempotent. So a subsequent call works (and does not report a change,changed=False
) as one would expect.This seems an implementation issue in the APIC.
PS If you would add
status="created,modified"
or simplystatus="modified"
your task will be idempotent and it will not lead to failures on subsequent runs.STEPS TO REPRODUCE
This will cause a failure on a subsequent create:
This will not cause a failure on a subsequent removal:
However using
status="modified"
will always work.This report wants to highlight that creation and deletion have a different behaviour.
The vendor has been notified of this inconsistency.
The text was updated successfully, but these errors were encountered: