Good catch. This patch works around the main problem that the mgmt server is passing broadcastUri in one way (e.g. vlan://100 in his example) for one Command and broadcastUri in another way (just '100') for a different Command. It doesn't affect fresh 4.3 installs because the way new values are stored in the DB make the code always pass 'vlan://100'. Daan and I are still discussing how to fix these.
On Tue, Jun 3, 2014 at 10:21 AM, Nux! <n...@li.nux.ro> wrote: > On 03.06.2014 16:20, Marcus wrote: > >> I think a fresh 4.3 install with vlan isolation is pretty well tested, but >> there have been issues with upgrades, and apparently basic/no isolation >> networks. I'm taking a shot in the dark to try to help, and I'll see if I >> can reproduce, but the symptoms seem rather complex and varied. If I can >> reproduce it, I can fix it. >> > > Thanks Marcus! I have 2 deployments, both fresh 4.3, one Adv and one > Adv+SG, neither exhibit this problem, so indeed it does look like an > upgrade issue. > It looks like someone attempted a fix, but without too much success > https://reviews.apache.org/r/21908/ .. > > Lucian > > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > >
