Search Engine: Elastic

Article ID: 130270, created on Feb 9, 2017, last review on Nov 3, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 6.0


Important: only OSA version 7.0 affected.

It is not possible to change network configuration of a VE, buttons 'Add IPv4 address' and 'Release' fail due to a task with the message:

[ApplicationUnknownError] [APS] {
"error": "APS::Util::OutOfResourceLimits",
"message": "Creation of resource with type '' is not allowed. Make sure that corresponding Resource is included into Subscription and does not exceed its limit."

Or "Execute operation 'change_environment_network'" task fails with errors like:

403 Forbidden
406 Not Acceptable

There were some change orders for IPv4 resource recently on the subscription, and there is a failed order pending provisioning.

The limit of the IPv4 address resource on Operations side does not match the amount of included IPv4 resource rates in Billing.

The amount of IP addresses listed for the VE in Provider's CP Cloud Infrastructure > Virtual Servers > Server_Name and in CCP does not match.


A race in VE network configuration change as a result of double click on Add IPv4 address button. The issue is going to be prevented by product improvement requests with IDs CCU-14047 and CCU-14266.


  1. Make sure the VE is not in transient state - there is no Configuring message in VPS tab in CCP.
  2. Cancel the pending Upsell "PACIVPSHostingVPS" for APS application Cloud Infrastructure and Execute operation 'change_environment_network' tasks.
  3. Cancel the pending failed orders.
  4. Order additional IPv4 resources in the amount of the difference between Operations in Billing (there should be a bigger limit in Operations side).
  5. Once the amount of addresses is synchronized, use CCP to downsell/upsell IP addresses normally and avoid double clicks not to run into the same issue again.
  6. In case of discrepancy between the actual IP addresses assigned in the VE and the list reflected in CCP, use the drop-ip OACI API request to remove the unnecessary IPs, example:

    [root@osscore ~]# cat reconfigure.xml
    <?xml version="1.0" encoding="UTF-8"?>
        <drop-ip ip=""/>
    [root@osscore ~]# curl -u'admin:***' -X PUT -d@reconfigure.xml -H "Content-Type: application/xml"

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF