Cannot find Python error

[robinren03]

Hi, I am new in GNS3, Ansible and SoNic (almost all related to this repo).

When I run

ansible-playbook deploy-sonic-dc-topology.yml -vvv

I run into an error

TASK [Get the server facts] ************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "/bin/sh: 1: /usr/bin/env python: not found\n", "module_stdout": "", "msg": "The module failed to execute correctly, you probably need to set the interpreter.\nSee stdout/stderr for the exact error", "rc": 127}

I changed the script of deploy-sonic-dc-topology.yml to the following as directed by the issues on Ansible

---
- hosts: localhost
  # Call the collections to use the respective modules
  collections:
    - davidban77.gns3
  vars:
    ansible_python_interpreter: "/root/miniconda3/bin/python"
    gns3_host: 192.168.1.34
    gns3_url: "http://{{ gns3_host }}"

However, I still face the same question of failing to find python. Could you please tell me what is happening? To my understanding, I only need one machine to run this script, as GNS3 should build a simulation (or emulation?) environment.

[cppmonkey]

Hi, Thanks for your interest in this repo.
I've had a good poke around over the last day or so.

The easiest way to resolve the issue, is to substitue the shebang within DavidBan77's Ansible module with the following command
sed -i -e 's/#!\/usr\/bin\/env python/#!\/usr\/bin\/python/g' ~/.ansible/collections/ansible_collections/davidban77/gns3/plugins/modules/*.py

The next issue is the incomplete template creation. Thankfully thats easy enough. We can use the GNS3a file from this website https://sonic.software/. And as long as we import the template and name it sonic latest we're good.

Then onto the next issue - Where a dependency injects an additional parameter, causing the project creation to fail.
I've pinned the dependency fixing that.
The project will contain all of the objects, but they're all ontop of each other. Once you've moved them around, you'll have something like this (Minus the cloud connection and switch)

The script continues but another issue crops up. Whilst the script was logging into the switches and making changes, the telnet loops weren't completing. I tried countless ansible.netcommon version before trying different versions of Ansible. This seems to be a bug in Ansible 7.0 and newer. So that has also pinned to <7.0.0.
And in doing so, i see that the node_type value is also required. So thats been added.

Now that it runs through the script, but the portchannel creation fails, because the interfaces already have IP's. This block has been moved to resolve this.

Now that everything runs, I can see the BGP summary is empty.

After relocating the original article, I copied the following config into /etc/sonic/config_db.conf, adjusting it for each node based on my variables.

"BGP_NEIGHBOR": {
          "12.0.0.1": {
              "asn": "64001",
              "holdtime": "180",
              "keepalive": "60",
              "local_addr": "12.0.0.2",
              "name": "Leaf1",
              "nhopself": "0",
              "rrclient": "0"
          },
          "32.0.0.2": {
              "asn": "64003",
              "holdtime": "180",
              "keepalive": "60",
              "local_addr": "32.0.0.1",
              "name": "Leaf2",
              "nhopself": "0",
              "rrclient": "0"
          }

 },

After reloading the config, most of the BGP sessions established. Some didn't, as there ip conflicts.
Adjustments were made and the final changes to BGP on each node

 sonic# configure terminal
 sonic(config)# router bgp 64002
 sonic(config-router)# address-family ipv4 unicast  
 sonic(config-router-af)# redistribute connected
 sonic(config-router)# end
 sonic#write

At last all of the switches were communicating and routing traffic. But it does mean that the final task Create BGP doesn't work as intended. But I suspect a number of things have changed with Azure SONiC in 3 years. One thing remains, it doesn't feel very polished or cohesive.

Anyhow, I hope that help you get the ball rolling