cloudstack: Cannot associate a public IP to a new isolated network (4.12.0.0)

ISSUE TYPE
  • Bug Report
COMPONENT NAME
Networking
CLOUDSTACK VERSION
4.12.0.0
CONFIGURATION

I’m running my tests against the simulator container which I configured with an advanced datacenter setup: python /root/tools/marvin/marvin/deployDataCenter.py -i /root/setup/dev/advanced.cfg

OS / ENVIRONMENT

N/A

SUMMARY

When creating an isolated network and then try to assign a public IP to the network, I get the following error:

{"errorcode":431,"errortext":"Network with UUID:a45c36c1-c9c4-458e-838d-1c7c7eea80a6 is in allocated and needs to be implemented first before acquiring an IP address"}

This worked fine with the 4.11.2.0 simulator container, but now fails with 4.12.0.0.

STEPS TO REPRODUCE

Create a new isolated (DefaultIsolatedNetworkOfferingWithSourceNatService) network using the createNetwork API call. Then try to assign a public IP using the associateIpAddress API call.

EXPECTED RESULTS

Don’t get any errors and get a network with a public IP that will be it’s source NAT IP.

ACTUAL RESULTS

A network without a public IP and this error:

{"errorcode":431,"errortext":"Network with UUID:a45c36c1-c9c4-458e-838d-1c7c7eea80a6 is in allocated and needs to be implemented first before acquiring an IP address"}

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 32 (17 by maintainers)

Commits related to this issue

Most upvoted comments

If you look at the CHANGELOG you’ll see that the CloudStack fix is not part of 1.4.1 but is merged into master and will be part of the 1.4.2 release.

Ok… And is there a chance we can get a 4.12.1.0 or something? As this means both Terraform and Packer will not be able to play nice with 4.12.x.x (https://github.com/hashicorp/packer/issues/7557).

I can fix that one specific issue, but updating to fully support 4.12.x.x will then not be possible.