> On Jan 29, 2018, at 16:45, Arun SAG wrote:
>
> If anyone is running into db race while running database in
> master-slave mode with async replication, The bug has been identified
> and getting fixed here
> https://bugs.launchpad.net/oslo.db/+bug/1746116
Thanks for your
Hello,
On Tue, Dec 12, 2017 at 12:22 PM, Arun SAG wrote:
> Hello,
>
> We are running nova-network in ocata. We use mysql in a master-slave
> configuration, The master is read/write, and all reads go to the slave
> (slave_connection is set). When we tried to boot multiple VMs
On Fri, 15 Dec 2017 18:38:00 -0800, Arun Sag wrote:
Here are the sequence of actions happen in nova-network
1. allocate_for_instance calls -> allocate_fixed_ips
2. FixedIPs are successfully associated (we can see this in the log)
3. allocate_for_instance calls get_instance_nw_info, which in
Hi Jay,
On Fri, Dec 15, 2017 at 1:56 PM, Jay Pipes wrote:
> Can you point us to the code that is generating the above? It seems that
> get_instance_nw_info() in the Yahoo! manager.py contrib module line 965 is
> trying to build network information for an empty list of
On 12/12/2017 03:22 PM, Arun SAG wrote:
This kind of how the logs look like
2017-12-08 22:33:37,124 DEBUG
[yahoo.contrib.ocata_openstack_yahoo_plugins.nova.network.manager]
Hello,
We are running nova-network in ocata. We use mysql in a master-slave
configuration, The master is read/write, and all reads go to the slave
(slave_connection is set). When we tried to boot multiple VMs in
parallel (lets say 15), we see a race in allocate_for_instance's