-
Notifications
You must be signed in to change notification settings - Fork 161
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
ios_snmp_server readonly community idempotency #971
Comments
I found out that 'Legacy IOS' uses @exeral Can you please check again with a newer version of |
I tested with cisco.ios 6.0.0
but it's the same,
the before/after are identical I'm also surprised ansible ends creating two communities where one have the community name in the acl field. but that's maybe another story |
@exeral That looks indeed weird^^ Can you also show use the task configuration and YAML values? |
Yes it's weird. it's not very critical but a bit annoying, so I'm curious what is the cause The task is:
snmp_location_datacenter is pulled from inventory and has value "in the racks" |
On my IOS-XE devices they also show in the config as I'm also running into this. Actually hit In the first case is as @exeral reported with
However if you have the boolean of
|
For reference our pip is locked to
and collection is set to
|
SUMMARY
when creating a read-only community, the task is always status changed despite there is no change to do
ISSUE TYPE
COMPONENT NAME
cisco.ios.ios_snmp_server
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
debian 9
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 15.0(2)SE10a, RELEASE SOFTWARE (fc3)
WS-C2960G-48TC-L
STEPS TO REPRODUCE
EXPECTED RESULTS
after two consecutive runs, task should not have the status "changed"
ACTUAL RESULTS
task status is always "changed"
I think the issue is that:
on Cisco running config it's:
snmp-server community community_name RO ADMIN-SUP
while ansible try to match this commands ?:
snmp-server community community_name ro ADMIN-SUP
Cisco config wants the readonly parameter UPPERCASE
The text was updated successfully, but these errors were encountered: