Question

There is a subscription that is billed on BA side (Active/Running), but there is no such subscription in OA. How could that happen?

Answer

Most probably the subscription has been removed with API (pem.removeSubscription). The following can be checked:

  • the tasks for services unprovisionining on OA side;

  • the logs for the time of the tasks if they exist, e.g.

    Nov 24 13:56:11 myosscore.com : INF [openapi-firewall:f31d7b70 1:25375:f31d7b70 OpenAPI ]: [ OpenAPI::Firewall::grant] Allowed call to Open API from trusted location (192.168.11.11).
Nov 24 13:56:11 myosscore.com : DBG [openapi-firewall:f31d7b70 1:25375:f31d7b70 OpenAPI ]: [ OpenAPI::Firewall::grant] <=== EXIT [0.000069]
Nov 24 13:56:11 myosscore.com : DBG [openapi-firewall:f31d7b70 1:25375:f31d7b70 OpenAPI ]: [ OpenAPI::MethodDispatcher::do_create_method] ===> ENTRY
Nov 24 13:56:11 myosscore.com : DBG [openapi-firewall:f31d7b70 1:25375:f31d7b70 OpenAPI ]: [ OpenAPI::MethodDispatcher::getMethodSignature] ===> ENTRY
Nov 24 13:56:11 myosscore.com : DBG [openapi-firewall:f31d7b70 1:25375:f31d7b70 OpenAPI ]: [ OpenAPI::MethodDispatcher::getMethodSignature] Dispatching method 'pem.removeSubscription'
Nov 24 13:56:11 myosscore.com : DBG [openapi-firewall:f31d7b70 1:25375:f31d7b70 OpenAPI ]: [ OpenAPI::MethodDispatcher::getMethodSignature] Method 'pem.removeSubscription' found in c
ache.
Nov 24 13:56:11 myosscore.com : DBG [openapi-firewall:f31d7b70 1:25375:f31d7b70 OpenAPI ]: [ OpenAPI::MethodDispatcher::getMethodSignature] <=== EXIT [0.000030]
Nov 24 13:56:11 myosscore.com : DBG [openapi-firewall:f31d7b70 1:25375:f31d7b70 OpenAPI ]: [ OpenAPI::MethodDispatcher::do_create_method] <=== EXIT [0.000071]
Nov 24 13:56:11 myosscore.com : DBG [openapi:192.168.11.11:987089 1:25375:f3ce2b70 OpenAPI ]: [ OpenAPI::LogMethodCalls::process] ===> ENTRY
Nov 24 13:56:11 myosscore.com : INF [openapi:192.168.11.11:987089 1:25375:f3ce2b70 OpenAPI ]: ==>>> Executing OpenAPI method 'pem.removeSubscription' with parameters: [{ 'subscription_id' => 1011111, } ]

We can see the call was made from 192.168.11.11, so check what the server is, are there any scripts or staff members who can call API from this server.

Internal content