You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is it possible that mtx-tool previously wrote the cds-upgrade-buildlog in all cases (error/failed)?
After running the upgrade, you will get a resulting status and a log file for each tenant. In case of an unsuccessful upgrade, consult the associated log file for details.
they're now missing for me, mtx-tool 0.7.10 + mtxs
Thanks, Andre
The text was updated successfully, but these errors were encountered:
Hi @andre68723, that's a known issue. Unfortunately cds-mtxs does not provide the same functionality that cds-mtx did.
With cds-mtxs, this information is written to log files on the running cf instances, but it's not exposed through a rest API, so I cannot consume it easily with the mtx-tool.
It's technically still possible to get the information with the following approach:
# get tenant upgrade logs for instance 0
cf ssh <mtx-cds-app> -i 0 -c 'tar cfz - app/logs/*.log' | tar xfz - -C temp
# get tenant upgrade logs for instance 1
cf ssh <mtx-cds-app> -i 1 -c 'tar cfz - app/logs/*.log' | tar xfz - -C temp
... etc. for all instances
You need a unix shell for this, i.e., it works out-of-the-box on Mac and Linux, but might need some extra finagling on Windows.
I want to automate this approach in mtx-tool at some point, but have not had the time too look into it yet. If someone wants to work on it, PRs are welcome...
Hi @rlindner81,
is it possible that mtx-tool previously wrote the cds-upgrade-buildlog in all cases (error/failed)?
After running the upgrade, you will get a resulting status and a log file for each tenant. In case of an unsuccessful upgrade, consult the associated log file for details.
they're now missing for me, mtx-tool 0.7.10 + mtxs
Thanks, Andre
The text was updated successfully, but these errors were encountered: