But before going to DaaS 9 you have to fix this lag. We checked the /var/log/slony before upgrade, and everything looked fine at that moment as you can see in this screenshotīut in the end it turned out there was replication lag… VMware says it cannot fix this and there are improvements in DaaS 9.
Once we had a tricky failure at the “Verifying slony failover status”. In the setup log look for, there you will find the exact step what failed. In these cases always logon to the new tenant appliance via the service provider, and look into /var/log/desktone/setup. This message does not give you the right information. With a tenant migration (step 6 in rundeck) to DaaS 9 it could fail with message:ĭaasError: ‘Tenant migration failed in TA_MIGRATING phase with error: : Guest process exited unexpectedly: 1’
0 kommentar(er)
