Skip to content
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

brocade_facts Not Getting Most Recent Facts #154

Open
Javedkhansiddiqui opened this issue Jun 13, 2024 · 2 comments
Open

brocade_facts Not Getting Most Recent Facts #154

Javedkhansiddiqui opened this issue Jun 13, 2024 · 2 comments

Comments

@Javedkhansiddiqui
Copy link

Javedkhansiddiqui commented Jun 13, 2024

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

Identity added: /runner/artifacts/3049029/ssh_key_data (/runner/artifacts/3049029/ssh_key_data)
ansible-playbook [core 2.13.8]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/runner/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.9/site-packages/ansible
  ansible collection location = /runner/requirements_collections:/home/runner/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/bin/ansible-playbook
  python version = 3.9.16 (main, May 31 2023, 12:21:58) [GCC 8.5.0 20210514 (Red Hat 8.5.0-18)]
  jinja version = 3.0.3
  libyaml = True




2) MY CODE

image





3) MY ALIAS FETCH RESULTS BY BROCADE_FACTS

ok: [my_server.cloud.domain.org] => {
    "GET_url": "https://********/rest/running/brocade-zone/effective-configuration?vf-id=128",
    "POST_url": "https://********/rest/logout",
    "ansible_facts": {
        "brocade_zoning": {
            "defined-configuration": {
                "alias": [
                    {
                        "alias_name": "PMAX_3319_1D04",
                        "member_entry": {
                            "alias_entry_name": "50:00:09:73:b0:33:dc:04"
                        }
                    },
                    {
                        "alias_name": "PMAX_3319_1D06",
                        "member_entry": {
                            "alias_entry_name": "50:00:09:73:b0:33:dc:06"
                        }
                    },
                    {
                        "alias_name": "SampleAlias4",
                        "member_entry": {
                            "alias_entry_name": "10:23:45:67:76:54:32:12"
                        }
                    },
                    {
                        "alias_name": "ansibleHost1",
                        "member_entry": {
                            "alias_entry_name": [
                                "aa:11:11:11:11:11:11:11",
                                "aa:22:22:22:22:22:22:22"
                            ]
                        }
                    },
                    {
                        "alias_name": "ansibleHost8",
                        "member_entry": {
                            "alias_entry_name": [
                                "aa:11:11:11:11:11:11:11",
                                "aa:22:22:22:22:22:22:22"
                            ]
                        }
                    },
                    {
                        "alias_name": "server_host0",
                        "member_entry": {
                            "alias_entry_name": "10:00:94:40:c9:d0:1d:a2"
                        }
                    },
                    {
                        "alias_name": "server_host2",
                        "member_entry": {
                            "alias_entry_name": "10:00:94:40:c9:d0:1d:a3"
                        }
                    },
                    {
                        "alias_name": "server_host3",
                        "member_entry": {
                            "alias_entry_name": "10:00:94:40:c9:d0:1d:e1"
                        }
                    },
                    {
                        "alias_name": "server_host4",
                        "member_entry": {
                            "alias_entry_name": "10:00:94:40:c9:d0:1d:e2"
                        }
                    },
                  
                ],





4) MANUAL CHECK BY CONNECTING TO SWITCH NOT GETTING THOSE ALIAS

server_host0
server_host2
server_host3
server_host4

image

@prasad-valmeti-broadcom
Copy link
Collaborator

Could you please share the FOS Ansible and FOS switch versions used for this test?
Also, please share the playbook used for alias creation.

@prasad-valmeti-broadcom
Copy link
Collaborator

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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants