| 2015-12-26 06:51:52 |
Li Ma |
description |
Here is the problem:
A network is created and written in neutron DB. At the meantime, Etcd cannot get the corresponding key 'lswitch', which causes unable to create subnet for this network.
The log file says that Etcd was disconnected at the network creation.
AFAIK, if the operation on Etcd fails, the DB transaction should also be rollbacked at the neutron DB side to prevent from updating DB records.
The related code in dragonflow/neutron/plugin.py:
def create_network(self, context, network):
with context.session.begin(subtransactions=True):
result = super(DFPlugin, self).create_network(context,
network)
self._process_l3_create(context, result, network['network'])
return self.create_network_nb_api(result) |
Here is the problem:
A network is created and written in neutron DB. At the meantime, Etcd cannot get the corresponding key 'lswitch', which causes unable to create subnet for this network.
The log file says that Etcd was disconnected at the network creation.
AFAIK, if the operation on Etcd fails, the DB transaction should also be rollbacked at the neutron DB side to prevent from updating DB records. This causes inconsistency of DB backkends.
The related code in dragonflow/neutron/plugin.py:
def create_network(self, context, network):
with context.session.begin(subtransactions=True):
result = super(DFPlugin, self).create_network(context,
network)
self._process_l3_create(context, result, network['network'])
return self.create_network_nb_api(result) |
|
| 2015-12-26 06:52:00 |
Li Ma |
description |
Here is the problem:
A network is created and written in neutron DB. At the meantime, Etcd cannot get the corresponding key 'lswitch', which causes unable to create subnet for this network.
The log file says that Etcd was disconnected at the network creation.
AFAIK, if the operation on Etcd fails, the DB transaction should also be rollbacked at the neutron DB side to prevent from updating DB records. This causes inconsistency of DB backkends.
The related code in dragonflow/neutron/plugin.py:
def create_network(self, context, network):
with context.session.begin(subtransactions=True):
result = super(DFPlugin, self).create_network(context,
network)
self._process_l3_create(context, result, network['network'])
return self.create_network_nb_api(result) |
Here is the problem:
A network is created and written in neutron DB. At the meantime, Etcd cannot get the corresponding key 'lswitch', which causes unable to create subnet for this network.
The log file says that Etcd was disconnected at the network creation.
AFAIK, if the operation on Etcd fails, the DB transaction should also be rollbacked at the neutron DB side to prevent from updating DB records. This causes inconsistency of DB backends.
The related code in dragonflow/neutron/plugin.py:
def create_network(self, context, network):
with context.session.begin(subtransactions=True):
result = super(DFPlugin, self).create_network(context,
network)
self._process_l3_create(context, result, network['network'])
return self.create_network_nb_api(result) |
|
