Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry-pick #12086 to 7.0: Don't generate autodiscover config when no port matches host hints #12141

Merged
merged 2 commits into from
May 28, 2019

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented May 9, 2019

Cherry-pick of PR #12086 to 7.0 branch. Original message:

On metricbeat, when the host autodiscover hint is used, and it includes
the port, one of the exposed ports has to match with the one in the
hint. If not, no configuration should be generated. If it is generated,
it will have empty hosts, what would lead to unexpected errors as the
ones seen in #8264.

Fixes #8264

…lastic#12086)

On metricbeat, when the host autodiscover hint is used, and it includes
the port, one of the exposed ports has to match with the one in the
hint. If not, no configuration should be generated. If it is generated,
it will have empty hosts, what would lead to unexpected errors as the
seen in elastic#8264.

(cherry picked from commit cc73643)
@jsoriano jsoriano requested a review from a team as a code owner May 9, 2019 14:28
@jsoriano jsoriano merged commit 6cb7f8f into elastic:7.0 May 28, 2019
@jsoriano jsoriano deleted the backport_12086_7.0 branch May 28, 2019 15:34
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…lastic#12086) (elastic#12141)

On metricbeat, when the host autodiscover hint is used, and it includes
the port, one of the exposed ports has to match with the one in the
hint. If not, no configuration should be generated. If it is generated,
it will have empty hosts, what would lead to unexpected errors as the
seen in elastic#8264.

(cherry picked from commit ba36dce)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants