The bug was fixed in LBaasV2 during November / December 2015 ... refreshing environment to latest LBaasV2 version to validate that the bug is invalid.
The bug was fixed in LBaasV2 during November / December 2015 ... refreshing environment to latest LBaasV2 version to validate that the bug is invalid.