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

Fix freebsd tests by setting hostname #4222

Merged
merged 1 commit into from
May 5, 2017

Conversation

ruflin
Copy link
Collaborator

@ruflin ruflin commented May 5, 2017

On freebsd the filebeat tests fail because no hostname is set. This change sets the hostname to beats-tester.

@exekias
Copy link
Contributor

exekias commented May 5, 2017

LGTM if it works, in theory freebsd.vm.hostname = "beats-tester" should do the job too
https://www.vagrantup.com/docs/vagrantfile/machine_settings.html

@ruflin
Copy link
Collaborator Author

ruflin commented May 5, 2017

Will change it to your solution as its much nicer. Makes me think if we should configure it for all hosts to be the same?

On freebsd the filebeat tests fail because no hostname is set. This change sets the hostname to `beats-tester`.
@ruflin ruflin force-pushed the freebsd-hostname branch from ee40204 to fa67d8a Compare May 5, 2017 10:41
@exekias
Copy link
Contributor

exekias commented May 5, 2017

It would make sense to me, yes

@ruflin
Copy link
Collaborator Author

ruflin commented May 5, 2017

@andrewkroh WDYT?
@exekias Could I just configure it at the top once with config.vm.hostname and it will be applied to all hosts?

@exekias
Copy link
Contributor

exekias commented May 5, 2017

Yes, that should work in theory

@exekias exekias merged commit 1b2d67a into elastic:master May 5, 2017
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