Open Javedkhansiddiqui opened 3 months ago
Could you please share the FOS Ansible and FOS switch versions used for this test? Also, please share the playbook used for alias creation.
I tested this with FOS Ansible 1.3.3 and switch 9.2 release, and the behavior is as expected. After the manual delete, facts show the updated alias information which is not alias is available. a) Create first alias attempt . ------------- via playbook --- successful b) Fetch first fact about alias ------------- via playbook --- successful c) I connected to switch and manually deleted that alias. [server_host0, server_host2, server_host3, server_host4] d) Then fact about alias ------------- via manual --- As i deleted , not showing Alias e) Fetch fact about alias ------------- via playbook --- still shows alias exist , why?? (Here it is not showing the deleted aliases)
Please share more details about the release versions as requested and the playbooks used. What is the behavior with the sample playbooks that are there in the collections like facts.yml and zoning_zone_members_add_only.yml ?
SAME USER [Ansible_test_user] ACTIVITY
a) Create first alias attempt . ------------- via playbook --- successful b) Fetch first fact about alias ------------- via playbook --- successful c) I connected to switch and manually deleted that alias. [server_host0, server_host2, server_host3, server_host4] d) Then fact about alias ------------- via manual --- As i deleted , not showing Alias e) Fetch fact about alias ------------- via playbook --- still shows alias exist , why?? f) Now Created Same alias attempt ------- via playbook --- says it already exist.
1) AWX TOWER CONFIGURATION
2) MY CODE
3) MY ALIAS FETCH RESULTS BY BROCADE_FACTS
4) MANUAL CHECK BY CONNECTING TO SWITCH NOT GETTING THOSE ALIAS
server_host0 server_host2 server_host3 server_host4