@Kptainflintt
You're facing 2 different issues:
- it seems the SDN Controller plugin cannot reach OVSDB
- the SDN Controller plugin does not cleanup when there is an issue
For 2. there is a work item to fix this on the XO team side. Just to clarify, what happens is that your request reached the XAPI, a network was created on the pool, then the SDN plugin tries to actually establish the tunnel, but fails as it cannot reach OVSDB, at that point you get the error, but the network have been created on your pool(s).
You can check to confirm that the tunnel is not established using ovs-vsctl show, when the network is established, you should see something that looks like:
Bridge xapi6
Controller "pssl:"
fail_mode: standalone
Port vif1.3
Interface vif1.3
Port xapi6
Interface xapi6
type: internal
Port xapi6_port1
Interface xapi6_iface1
type: gre
options: {key="11", remote_ip="192.168.1.220"}
Of course it could be vxlan instead of gre, but the remote_ip part is the important point. Here I believe you won't see that. And you'll have to manually remove these networks from your pool(s).
Regarding 1. and the connexion refused error, that probably means the 6640 port was not opened in the firewall. This should have been done automatically by XAPI.
You can check if that's the case:
# iptables-save | grep 6640
-A xapi-INPUT -p tcp -m conntrack --ctstate NEW -m tcp --dport 6640 -j ACCEPT
If you don't have that rule you can search your /var/log/xensource.log* for openvswitch-config-update and see if there are any errors there.
