Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cds-upgrade-buildlog* #32

Open
andre68723 opened this issue May 26, 2023 · 1 comment
Open

cds-upgrade-buildlog* #32

andre68723 opened this issue May 26, 2023 · 1 comment

Comments

@andre68723
Copy link

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

@rlindner81
Copy link
Contributor

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants