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

Don't ignore 'private_ips' unnecessarily #46243

Merged

Conversation

mark-hyde
Copy link
Contributor

What does this PR do?

Removes a test for the existence of a private_ip in an earlier list of private_ips where salt-cloud has been told to use private_ips for ssh access.

What issues does this PR fix or reference?

#46215 salt-cloud will only intermittently build rackspace cloud instances with purely private networks

Previous Behavior

salt-cloud ignores valid private_ip addresses assigned by the API

New Behavior

If ssh_interface is 'private_ips' then check whether IP is in ignore_cidr range, but don't ignore the IP if it was found in the original list of private_ips which was gathered when the new instance was created.

Tests written?

No

Commits signed with GPG?

No

Please review Salt's Contributing Guide for best practices.

See GitHub's page on GPG signing for more information about signing commits with GPG.

- Looks like this was originally introduced to resolve an issue with HP
servers putting public_ips in the private_ip list.
- The code has been refactored several times since then.
- This affects the code where 'ssh_interface: private_ips' so we by
definition do not want to use public_ips anyway.
- The original code prevents servers with only private_ips (e.g on
some rackconnect_v3 servers) from building as salt-cloud thinks the
private_ips are not valid.
- ISSUE saltstack#46215
@rallytime rallytime merged commit 53067cc into saltstack:2017.7 Feb 28, 2018
@mark-hyde mark-hyde deleted the fix-openstack-private-network-issue branch March 22, 2018 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants