Jeff, We had several VR issues in the testing of 4.7.1, including this one. We fixed it by removing unused IPs from ips.json. As there are lot of changes between 4.7.1 and master, I do not know the current status in master/4.10 PR 1907 seems to fix this issue (not tested). There might be other issue caused by unused IPs in ips.json.
-Wei 2017-03-01 14:41 GMT+01:00 Jeff Hair <j...@greenqloud.com>: > Yes, i know it's been merged. The problem is that this issue seems to come > up "randomly" (of course, nothing is ever really random), and I was > wondering if anyone else has run into it. > > My initial testing of PR 1907 hasn't yielded the issue happening yet, and > the only place I've seen it so far is on a router that doesn't have 1907 > applied. But I'm not convinced that it won't happen ever after applying > 1907... > > *Jeff Hair* > Technical Lead and Software Developer > > Tel: (+354) 415 0200 > j...@greenqloud.com > www.greenqloud.com > > On Wed, Mar 1, 2017 at 1:39 PM, Wei ZHOU <ustcweiz...@gmail.com> wrote: > > > PR 1907 has been merged. You can test with it. > > > > > > 2017-03-01 14:12 GMT+01:00 Jeff Hair <j...@greenqloud.com>: > > > > > Hi, > > > > > > In the testing of PR 1908 (https://github.com/apache/ > > cloudstack/pull/1908 > > > ), > > > it has come up that some IPs which are removed from the router get put > > into > > > the /etc/cloudstack/ips.json data bag with add = True. This causes the > > IPs > > > to be re-added to the interface and arpinged, breaking connectivity and > > > causing IP conflicts. > > > > > > Does anyone know anything about this? Is it due to old routers that > were > > > affected by CLOUDSTACK-9500 (fixed in PR 1907), or is this behavior > still > > > actively happening on master? > > > > > > Jeff > > > > > >
