Comment 3 for bug 1495423

To clarify a little on the distinction between the two bugs: In this case, we cannot actually use monitor as the OVS instance is running in Dom0 (control domain) where as the neutron code is running in DomU (The version of Python in Dom0 is too ancient to run Neutron)

Bug 1493662 is relating to how the paths for the command is identified: There is an expectation that the command (without absolute paths) has an exact match, but in the XenServer tests the paths have a prefix. It's very possible that fixing this bug will work around Bug 1493662, but it's also possible that we need to fix both of them to get XenServer using ovsdb-client monitor.