-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Closed
Copy link
Description
problem
If an account has reached its public IP address limit, when we attempt to enable static NAT for an already acquired public IP in VPC network results in an error. The error logs indicate that the account has exceeded its limit.
Also enabling static NAT for the already acquired Public IP address in the Isolated network works fine.
Error Log:
2025-03-04 22:04:54,197 ERROR [c.c.n.IpAddressManagerImpl] (qtp1404565079-40920:[ctx-d414f824, ctx-1f564ff0]) (logid:71e1cb69) Failed to associate ip address Ip[103.244.247.49-1] to network Network {"id": 562, "name": "testLab", "uuid": "ec7f21a6-f7d9-4374-8d86-b8473367c71d", "networkofferingid": 13} com.cloud.exception.ResourceAllocationException: Maximum amount of resources of Type = 'public_ip', tag = 'null' for Account Name = [email protected] in Domain Id = 8 is exceeded: Account Resource Limit = 6, Current Account Resource Amount = 6, Current Account Resource Reservation = 0, Requested Resource Amount = 1.
versions
ACS 4.20
The steps to reproduce the bug
- Create an account with a public IP address limit of 2.
- Obtain all available public IP addresses within the account until the limit is reached in the VPC network
- Enable Static NAT for the acquired public IP addresses to an instance
- Getting the below error when the limit for the account has been reached.
What to do about it?
No response
