Hi George,
Sorry for the late reply, but I’m glad that you managed to figure it out.
The addition of the configurations cta.instance_name and cta.schedulerdb.scheduler_backend_name was indeed a non-backward compatible change, introduced by the previous stable release 5.11.2.0-1.
It’s referenced in the announcement through a link, but I realise that it might have gone unnoticed…
For reference, in case anyone else looks into this thread, the details about these new configurations required for 5.11.2.0-1 (and later) can be found here.
Also, thank you for also sharing the solution that worked for you regarding the other problems.
I’m not sure why cta-taped took such a long time to be visible, but the logs should provide some useful details if the initialisation failed.
Best,
Joao