[cmd/opampsupervisor] fix: Clear config timeout timer & send APPLIED remote config status when running nop config #36733
+86
−8
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.
Description
When sending a nop config to the supervisor, it does not start the collector. However there is a config timeout that would report an error back to the OpAmp server in this case, despite the agent technically being healthy.
This change clears the config timeout when we aren't starting the agent due to a nop config. It also reports an 'Applied' remote config status, since to the OpAmp server it should appear as if it the collector is successfully running the config.
Link to tracking issue
Fixes #36682
Testing
Updated an e2e test to apply an empty config and verify an 'Applied' status is returned by the supervisor.