Closed samuellay closed 2 years ago
Hi Samuellay, To understand better on this issue, “error-message": "Error: Duplicate members exist in the member list of \"mypeerzone\". To avoid unexpected behavior please create peer zones without duplicate members.", need some more details as mentioned below:
As per the zone module owners, we need the membership details of the aliases the user has specified as Peer Zone members:
"The fcaliases, (secondtolaststhost, lasthost) were previously created exclusively for this test."
Could you please send these details to understand why it shows issue? As per the understanding these alias members are already exist that's why it shows that message. Regards, Prasad
The principal members did not exist prior to running the command. Even it they were, the correct ansible behavior would be to run successfully w/ 0 changes.
Hi Samuellay, Ansible sends the config request to the switch, the response is directly coming from the switch. No membership validation is performed on Ansible side.
As per the zone module owner, secondtolaststhost, and lasthost alias members already exist on the switch that is attempting to create
peer zone. In those scenarios only, the "Error: Duplicate members exist in the member list of \"peerzone003\". To avoid unexpected behavior please create peer zones without duplicate members." appears.
Could you please confirm if there are alias members exist on the switch before running the test?
If they do exist, what does the membership of these aliases look like?
Could you please provide these details that will help to make progress on this issue?
Regards, Prasad
Yes, I was misinterpreting the error message. I thought it meant duplicates in the current argument set. I finally realized that this was because those wwpns were already zoned to those targets with different fcaliases. I had failed to clean up adequately after some previous testing.
Thank you for the follow-up, Sam
I can't create peer zones. The plugin is supposed to recognize "principal_members" and create a peer zone. When I use normal members at zone creation, it works:
When I use principal members, I get an error saying I'm using duplicate names.
Here's the information:
Requirements.txt:
Playbook:
Role:
Inventory:
Parameter files:
zones2.yml
Run with principalmembers:
**It fails with principal members above Look for
"error-message": "Error: Duplicate members exist in the member list of \"mypeerzone\". To avoid unexpected behavior please create peer zones without duplicate members.",**
Now try with initiators:
Works for initators, but not principal members
PLAY RECAP ***** syn14b01fc001 : ok=1 changed=1 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0