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

Cannot choose network during VM deployment on UI #3570

Closed
GabrielBrascher opened this issue Aug 26, 2019 · 0 comments · Fixed by #3571
Closed

Cannot choose network during VM deployment on UI #3570

GabrielBrascher opened this issue Aug 26, 2019 · 0 comments · Fixed by #3571

Comments

@GabrielBrascher
Copy link
Member

ISSUE TYPE
  • Bug Report
COMPONENT NAME
UI and Network (NetworkModelImpl)
CLOUDSTACK VERSION
+4.12
CONFIGURATION

This issue happens when a network has all the following characteristics:

  • advanced networking with security groups
  • traffic type of "Guest"
  • guest type of "Shared"
  • IPv6 cidr not null
SUMMARY

The Javascript code adds the parameter canusefordeploy=true on the API call when the network is an advanced network with security groups. With that, the endpoint (management server) expects "canUseForDeploy" == true; however, the returned value is false due to not finding IPv6 addresses available in the network which makes the UI to not list the networks.

Table "user_ipv6_address" (UserIpv6AddressVO) is empty and will always be (as it is a legacy code/table, not used in any IP allocation flow). I will be soon sending a PR fixing it by removing that IPv6 address verification.

@GabrielBrascher GabrielBrascher added this to the 4.13.0.0 milestone Aug 26, 2019
@GabrielBrascher GabrielBrascher self-assigned this Aug 26, 2019
@GabrielBrascher GabrielBrascher changed the title Cannot choose network on UI when network has SG and IPv6 cidr not null Cannot choose network during VM deployment on UI Aug 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant