Repository navigation
Cleanup complicates error-analysis for bosh create-env #659
Description
Activity
- moved this to Inbox in Foundational Infrastructure Working Group
on Aug 27, 2024 In absence of this feature, have you tried:
export BOSH_LOG_LEVEL=debug?- moved this from Inbox to Pending Review | Discussion in Foundational Infrastructure Working Group
on Sep 5, 2024 Yes, it did not help me.
- moved this from Pending Review | Discussion to Waiting for Changes | Open for Contribution in Foundational Infrastructure Working Group
on Sep 26, 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?