Fix adding cloud-init logs to diagnostics archive #3710
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EzzhevNikita
approved these changes
Jan 21, 2022
DaniilShmelev
approved these changes
Jan 21, 2022
anatolybolshakov
approved these changes
Jan 21, 2022
AndreyIvanov42
pushed a commit
to AndreyIvanov42/azure-pipelines-agent
that referenced
this pull request
Jan 24, 2022
* Fix adding cloud-init logs to diagnostics archive * Add debug message when logs not found
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix adding cloud-init logs to diagnostics archive. Added check for the existence cloud-init logs file before copying it.
Checked cases: