On Thu, Oct 2, 2014 at 11:49 AM, Rohit Yadav <rohityada...@gmail.com> wrote:
> This null check sort of masks the issue that Mgmt server was expecting some > configuration which does not exist anymore and in this fix we're simply > ignore when this happens. Should we at least log a warning that a config > was not found anymore? > you are right about the warning, i will add > > While it's right for most cases but when someone is upgrading from one > version of CloudStack to another, we deliberately ignore missing (null) > configs that don't exist anymore which may affect CloudStack's behaviour. > as said this is not solving the upgrade issue and we still need to figure out a solution for that. -- Daan
