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.

Sign up for GitHub

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

Jump to bottom

No support for network interfaces without public IPs #76

Closed
alparslanavci opened this issue Apr 7, 2021 · 0 comments · Fixed by #77
Closed

No support for network interfaces without public IPs #76

alparslanavci opened this issue Apr 7, 2021 · 0 comments · Fixed by #77
Assignees
@alparslanavci
Labels
bug
Milestone
2.1.1

Comments

@alparslanavci
Copy link
Contributor

When a VM is created with a network interface without a public IP, the discovery plugin doesn't add it to the candidate instances list (See here). This should be fixed in order to support internal Hazelcast cluster setups.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alparslanavci alparslanavci

Labels
bug
Projects
None yet
Milestone
2.1.1
Development

Successfully merging a pull request may close this issue.

Changed publicIp check to privateIp when parsing API response [CN-47] alparslanavci/hazelcast-azure
1 participant
@alparslanavci