f5-ansible icon indicating copy to clipboard operation
f5-ansible copied to clipboard

Fully Qualifying Module for ConfigSync Fails Finding Device Group

Open polskikrol opened this issue 3 years ago • 3 comments

COMPONENT NAME

bigip_configsync_action_result

Environment

ANSIBLE VERSION
TOWER 3.8.4, ANSIBLE 2.9.27
BIGIP VERSION
BIGIP 14.1.2.6
SUMMARY

Have both v1 latest and v2 collections installed. When defaulting to v1 and using 'bigip_configsync_action:' everything works, however, when using 'f5networks.f5_modules.bigip_configsync_action:' (fully qualifying the module), receive an error as follows: 'The specified 'device_group' not not exist.'. Yes, looks like an error grammar mistake as well... should be 'does not' exist. Nevertheless, checking via debug output, the device_group variable being passed is essentially '/Common/device-group-name-here' as previously. So not sure why this is failing when fully qualifying the module.

polskikrol avatar Nov 11 '21 17:11 polskikrol

Checking icrd logs, the following error is noticed: 'Ignorning unexpected json property at configuration item /cm/device-group. The json property is "Common".'

As a reminder, I am grabbing the name of the failover device group using the normal method of collecting facts and capturing the full_path param.

Oddly enough, removing the partition element this works when being fully qualified. Almost like the parsing is being done differently depending on how the module is referenced!

polskikrol avatar Nov 11 '21 20:11 polskikrol

So that is messed up....

Using 'bigip_configsync_action' as the task you can pass device_group as '/Common/name_of_group'. HOWEVER, Using 'f5networks.f5_modules.bigip_configsync_action' as the task, fully qualified, the parser cant handle the '/' forward slash and you need to filter through the variable through '| replace("/", "~")'. So something is a bit amiss here.

polskikrol avatar Nov 11 '21 21:11 polskikrol

@polskikrol - Please share the playbook to try this at our end.

trinaths avatar Nov 18 '21 06:11 trinaths

Closing this now. Reopen if you still face the issue. Thanks!

KrithikaChidambaram avatar Nov 30 '22 17:11 KrithikaChidambaram