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

Provide IPv6 mask for IPv6 virtual servers. #1295

Closed

Conversation

marbindrakon
Copy link

@marbindrakon marbindrakon commented Mar 28, 2018

The VIP netmask was always given as 255.255.255.255 which caused errors
when placing a Neutron LB on an IPv6 subnet. This passes the proper /128
mask for IPv6 virtual server IP addresses.

@richbrowne

What issues does this address?

Fixes #1294
...

What's this change do?

This change causes the agent to pass "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff" as the netmask for IPv6 VIPs rather than the previous value of 255.255.255.255. I did not do testing with IPv6 pool members.

Where should the reviewer start?

service_adapter.py

Any background context?

This resolves a failure to provision a Neutron LB on an IPv6 subnet. In the test scenario, the LB is placed on a shared IPv6 subnet while the backends are on an IPv4 tenant network.

The VIP netmask was always given as 255.255.255.255 which caused errors
when placing a Neutron LB on an IPv6 subnet. This passes the proper /128
mask for IPv6 virtual server IP addresses.
@marbindrakon
Copy link
Author

Can somebody re-run the CI for this commit? I don't see any failures related to the changed code.

@hlesesne
Copy link

Bump.

@marbindrakon
Copy link
Author

Closing this PR as it is 3 years old now

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.

Agent attempts to pass IPv4 netmask for IPv6 virtual server
2 participants