Slawek, you added the gate-failure tag for tricircle, right? The neutron gate does not seem to be broken by this.
While I don't understand the tricircle test environment yet, it seems to me tricircle should adapt to neutron to fix this and not the other way around because tricircle depends on private neutron methods:
File "tricircle/network/managers.py", line 65, in create_network_segments
segments = self._process_provider_create(network)
File "/opt/stack/neutron/neutron/plugins/ml2/managers.py", line 116, in _process_provider_create
return [self._process_provider_segment(segment)]
So maybe we can remove neutron from the list of affected components? Do we know of any other networking-* project which may be broken? The first handful errors I've seen in kibana all came from tricircle.
Slawek, you added the gate-failure tag for tricircle, right? The neutron gate does not seem to be broken by this.
While I don't understand the tricircle test environment yet, it seems to me tricircle should adapt to neutron to fix this and not the other way around because tricircle depends on private neutron methods:
File "tricircle/ network/ managers. py", line 65, in create_ network_ segments provider_ create( network) neutron/ neutron/ plugins/ ml2/managers. py", line 116, in _process_ provider_ create process_ provider_ segment( segment) ]
segments = self._process_
File "/opt/stack/
return [self._
So maybe we can remove neutron from the list of affected components? Do we know of any other networking-* project which may be broken? The first handful errors I've seen in kibana all came from tricircle.