Reduce noise when using Node 20 for container startup#5506
Open
baarde wants to merge 2 commits intomicrosoft:masterfrom
Open
Reduce noise when using Node 20 for container startup#5506baarde wants to merge 2 commits intomicrosoft:masterfrom
baarde wants to merge 2 commits intomicrosoft:masterfrom
Conversation
Author
|
@microsoft-github-policy-service agree |
kllysng
approved these changes
Mar 26, 2026
paulmedynski
approved these changes
Apr 10, 2026
|
@microsoft/azure-pipelines-platform - This seems like a simple change and would eliminate spurious warnings from pipeline runs. Will this be prioritized for an upcoming release? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Context
This PR fixes noisy container startup logging introduced with the Node24 / Node20 fallback flow in #5419.
When Node 20 is the expected startup path, the agent currently logs a warning (
Using Node 20 for container startup.) even though no fallback occurred.Related issue: #5464
Description
This change updates logging in
ContainerOperationProvider.csandContainerOperationProviderEnhanced.cs:Node 24success logs atDebugNode 20success logs atDebugwhen it is the expected pathNode 24toNode 20remains aWarningThis keeps warnings for real degraded behavior and removes noise from normal startup.
Risk Assessment (Low / Medium / High)
Low
No changes except for logging.
Unit Tests Added or Updated (Yes / No)
No
Additional Testing Performed
None
Change Behind Feature Flag (Yes / No)
No
Tech Design / Approach
Apply the same log-level adjustment in both implementations so behavior stays consistent.
Documentation Changes Required (Yes/No)
No
Logging Added/Updated (Yes/No)
Yes
Adjusted log levels so expected startup paths use
Debugand real fallbacks keepWarning.Telemetry Added/Updated (Yes/No)
No
Rollback Scenario and Process (Yes/No)
No
Dependency Impact Assessed and Regression Tested (Yes/No)
No