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

Cleanup complicates error-analysis for bosh create-env #659

Open
joergdw opened this issue Aug 27, 2024 · 2 comments
Open

Cleanup complicates error-analysis for bosh create-env #659

joergdw opened this issue Aug 27, 2024 · 2 comments

Comments

@joergdw
Copy link

joergdw commented Aug 27, 2024

When using bosh create-env, the cli may start quite some sub-processes to compile releases. It works on some temporary directories looking like ${HOME}/.bosh/installations/<some-uuid>/tmp/<release-folder>.

Folders in there get cleaned-up after the bosh-cli finishes. This happens as well in case of an error. This however is unfortunate and significantly complicates debugging. Can the bosh-cli please either not delete these directories in case of an error or – at least – offer a cli-option to keep everything within the working-directories?

@rkoster
Copy link
Contributor

rkoster commented Sep 5, 2024

In absence of this feature, have you tried: export BOSH_LOG_LEVEL=debug?

@rkoster rkoster moved this from Inbox to Pending Review | Discussion in Foundational Infrastructure Working Group Sep 5, 2024
@joergdw
Copy link
Author

joergdw commented Sep 25, 2024

Yes, it did not help me.

@jpalermo jpalermo moved this from Pending Review | Discussion to Waiting for Changes | Open for Contribution in Foundational Infrastructure Working Group Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Waiting for Changes | Open for Contribution
Development

No branches or pull requests

2 participants