all of 0 customers running across it so far,
2 admins poking at it, one being myself trying to get Ansible playbooks to play nicely with this new pair.
Playbook functions on old MDS’s without an incident. that is one MINOR code version behind (like .1a to .2)
The error: "msg": "zone has acquired lock on the switch for vsan 101. Hence cannot procced.",
some redactions have been made.
I think I found the offending “Check” thats causing my headache.
`
# Step1: execute show zone status and get
shZoneStatusObj = ShowZoneStatus(module, vsan)
sw_default_zone = shZoneStatusObj.getDefaultZone()
sw_mode = shZoneStatusObj.getMode()
sw_smart_zoning = shZoneStatusObj.getSmartZoningStatus() if sw_smart_zoning.lower() == "Enabled".lower():
sw_smart_zoning_bool = True
else:
sw_smart_zoning_bool = False if shZoneStatusObj.isVsanAbsent():
module.fail_json(msg='Vsan ' + str(vsan) + ' is not present in the switch. Hence cannot procced.') if shZoneStatusObj.isLocked():
module.fail_json(msg='zone has acquired clock on the switch for vsan ' + str(vsan) + '. Hence cannot procced.')
`
Referencing the ShowZoneStatus module that its calling
Looks like its mishandling the output from this command…