Cherry-pick #21173 to 7.x: Fix remote_write flaky test #21193
Merged
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.
Cherry-pick of PR #21173 to 7.x branch. Original message:
What does this PR do?
This PR fixes the flaky
remote_write
system test. The issue should be due to docker networking since thehttp://host.docker.internal:9201/write
endpoint seems to not be working properly and we can stick withhttp://0.0.0.0:9201/write
only...I tested locally (on macOS) with
MODULE=prometheus mage -v pythonIntegTest
and seems to work now. Let's see if CI is happy too.Why is it important?
To enable back the system test for the
remote_write
metricset.Related issues