Search Engine: Elastic

Article ID: 130116, created on Jan 6, 2017, last review on Apr 7, 2017

  • Applies to:
  • Operations Automation
  • Business Automation

Symptoms

An attempt to destroy an APS 2.0 Windows Azure Pack subscription in Billing times out.

Corresponding pem.removeSubscription call ends with the following error in /var/log/poa.log:

DBService invocation error: IJ000459: Transaction is not active: tx=TransactionImple < ac, BasicAction: 0:ffff0a146601:-22a4fa1c:58546f93:6b9c45 status: ActionStatus.ABORTED 

Tracing the call execution in the log, consecutive unprovisioning of Azure add-on instances can be spotted:

Jan  5 05:29:50 osscore : INF [openapi:10.20.101.1:211009 1:7893:a7696b70 SAAS ]: [ APSC] [Provision] begin unprovision of resource c54ef5a1-f39f-4495-b8a3-b0178cbba7a6 of type 'addon-instances' (http://www.parallels.com/infrastructure/cloudos/addon-instance/1.0) for APS application 'Windows Azure Pack APS Package-1.4-299'
Jan  5 05:29:51 osscore : INF [openapi:10.20.101.1:211009 1:7893:a7696b70 SAAS ]: [ APSC] [Provision] begin unprovision of resource 16f61460-750f-48ff-b648-e11d1b78f4f4 of type 'addon-instances' (http://www.parallels.com/infrastructure/cloudos/addon-instance/1.0) for APS application 'Windows Azure Pack APS Package-1.4-299'
Jan  5 05:29:51 osscore : INF [openapi:10.20.101.1:211009 1:7893:a7696b70 SAAS ]: [ APSC] [Provision] begin unprovision of resource ef716f23-7dda-4885-8bdf-f54b3dd51cb1 of type 'addon-instances' (http://www.parallels.com/infrastructure/cloudos/addon-instance/1.0) for APS application 'Windows Azure Pack APS Package-1.4-299'

The overall amount of "WAP Add-on instance" resources is large for this subscription.

The same symptoms may appear for the case of downgrading Windows Azure Pack resources in a subscription, the corresponding change order fails with a similar error:

DBService invocation error: IJ000459: Transaction is not active: tx=TransactionImpl

The same symptom applies to subscription renewal orders, if the subscription is disabled.

Cause

Default OA transaction timeout is not enough to process the total amount of subscription resources.

Resolution

In case of subscription renewal, it is necessary to estimate the amount of time to create the amount of add-ons on the subscription and increase PAU timeout accordingly. It is very important to decrease the timeout back, once the order is processed.

In case of subscription removal, use the attached delete-wap-addons.py script on OA Management Node to remove the resources prior to destroying the subscription. The example of invocation:

# python delete-wap-addons.py 1000011 1000021

where 1000011 is the account ID of the subscription owner and 1000021 is the subscription ID.

Note: the script execution also takes a large amount of time, depending on the resources amount. Rough estimation is 1500 resources x 1 hour.

In case of downgrading resources, the necessary amount of add-ons can be deleted manually. Request Odin Support assistance in this case.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae

Email subscription for changes to this article
Save as PDF