Cortex 3.0 upgrade issue
papiyachatterjee opened this issue · 3 comments
hi @papiyachatterjee , without any more details on your implementation, I'd guess this is because your setting.yaml config file in 2.0 had the default for vbrp as RUNTIME) and is now switched to behave as a table. I'd recommend not merging configuration files and only adding new values instead, as your configurations will work for your needs better than the examples we include in them.
If switching the value back to runtime does not fix it, please provide more context on what vbrp looks like today.
Hi @papiyachatterjee , just wanted to follow up on this open issue. Did the suggestion from @Lsubatin help or do you have further questions on this topic? If so, please provide us with a bit more context on what your current setup looks like and how you have tried to execute the upgrade.
Closing this issue as inactive. If there are still open questions, please let us know and we will be happy to assist you.