Original Publishing Date: 2023-05-18 Symptoms In an attempt to add payment method in UX1, the error 'Current Account can not process transaction: wrong Transaction ID.' appeared after authentication process and payment method was not saved. Cause The error appears when L0, L1 or L2 staff member impersonates into customer, log in to customer UI and tries to create payment method or place payment. Adding stored payment method was prohibited for user other than the end customer. This action requires the customer user to login directly using his username and password and add payment method or place payment. Resolution End customer is required to add payment method or place payment by logging in directly using their own user and password.

Original Publishing Date: 2023-05-18 Symptoms Try to schedule a Change Order on Renewal date shows following message in UX1: You has passed the cancellation window for reducing seats for this subscription Cause This is caused by software issue #PDI-2035 or #PDI-2096. PLM sends draft request to Connect with planned_date as null so it is not considered as a scheduled for renewal change but immediate. Resolution Immediate work around to place order is click 'Next' button again, at second attempt to validate the order the planned_date is passed to the Connect request. Software issue #PDI-2035 is planned to be fixed in PLM version 1.11. Software issue #PDI-2096 is planned to be fixed in PLM version 1.12.

Original Publishing Date: 2023-05-10 Symptoms The Azure NCE subscription import process got stuck from CB Connect with an error in the PR request "Error on allowing the customer to view charges. : There has not been possible to identify billing account". Cause This message appears due to the GET request received an empty reply and it's visible from CB Connect logs: "GET" : "https://management.azure.com/providers/Microsoft.Billing/billingAccounts/?api-version=2019-10-01-preview", x-ms-request-id:"b2d30be9-1e24-40b8-9f42-77997b6d7dcf": {'value': []} It means a customer doesn't have a provider billing account set up with Microsoft, which is why an empty value was received. Resolution That needs to be fixed by a customer with Microsoft.

Original Publishing Date: 2023-05-19 Symptoms Received below error when trying to place an order via API or CP: Could not invoke endpoint url 'https://order-management:8081/rest/order-management/3c0d0ab8-4466-422b-845c-2471e3af534a/orders' of application instance with UUID '15000493-c7a5-481d-94fd-f47e2a6b6e51'. RESTEASY004655: Unable to invoke request: java.net.UnknownHostException: order-management: Name or service not known: order-management: Name or service not known Cause order-management pod is not available or accessible from MN node. Resolution Please check if order-management pod is running: [root@ooamn ~]# kubectl get pod | grep order-management order-management-d4f44d686-mt9fr 1/1 Running 2426 (76m ago) 106d If it is running, please make sure connection from MN node is available by testing using telnet: [root@ooamn ~]# telnet order-management 8081 Trying 10.107.1.32... Connected to order-management. Escape character is '^]'. If kubectl command produce output that is similar as below snippet, it means that your kubernetes cluster is not reachable. Please check and rectifty any issue with kubernetes cluster networking: [root@ooamn ~]# kubectl get pod Unable to connect to the server: dial tcp 192.168.0.1:6443: i/o timeout If kubectl command doesn't show any output, you need to deploy order-management pod as per the official documentation here: Deploying Order Management If you need further assistance of error that is not mentioned above, please contact Cloudblue Technical Support.

Original Publishing Date: 2023-05-19 Symptoms Place a Cancellation order for product "Ready Data Center Pay As You Go" and get failed with error similar to this:  Service Destroyed: Removal of Service of Subscription #1351515 is failed. Stopping service of Order Item #18461110 failed: Stopping service for Subscription #1351515 failed: Platform error #error_code #-1, extype_id #-1, module_id #, '500 Internal Server Error' received from 'PUT https://XX.XX.XX.XX:443/vPoint/vdc/aa50ed10-d6dd-4950-803a-cea55d028947/disable': POST https://vendorEndpotinDomain/api/sessions failed, return code: 406, error: , request data: Cause The command sent from endpoint was rejected by vendor due to unsupported API version.  Resolution Please, contact CloudBlue Technical Support in order to fix. Have in mind this product is no longer supported and the solution will only complete Cancellation Order in CloudBlue Commerce, if this subscription is still active in Vendor side it should be needed to contact Vendor and ask to disable it on their side.

Original Publishing Date: 2023-05-22 Symptoms Customer would like to use local cache repository for docker and helm for Cloudblue installation. The setup-product.sh script does not recognize the local cache repository, leading to an inability to fetch necessary resources, resulting in failed installation or potential inconsistencies in deployments. Cause Helmfile-deploy project currently does not support the use of a local cache repository for helm and docker. Software issue with id #OA-34948, should be fixed in the next 21.x patches. Resolution Please communicate with your Technical Account Manager if there is any update on this issue, or check Release notes on our sites.

Original Publishing Date: 2023-05-19 Symptoms Report generated using Subscription Dataset only contains 34 out of the 39 fields mentioned in Fields in the Subscriptions Data Set. Missing fields: SUBSCRIPTION_SUSPENSION_CODE SUBSCRIPTION_SUSPENSION_REASON SUBSCRIPTION_TERMINATION_CODE SUBSCRIPTION_TERMINATION_REASON SUBSCRIPTION_PERIOD_TYPE Cause There was no such columns in this report, this is documentation Issue, being fix in DOC-3279. Resolution Please communicate with your Technical Account Manager if there is any update on this issue, or check Release notes on our sites.

Original Publishing Date: 2023-05-23 Symptoms A Change Order is failed and has caused inconsistencies between OSS and BSS. The changes should have not reached MSFT and the new resource should be in 'Provisioning' status, whereas the old resource should be in 'Failed' status.  The order is failing due to the following reason: The order provisioning failed. The last error is "Task "Delivering event 'Resource limits changed' for APS application inhouse-products(https://inhouse-products:8081/rest)" (id = XX) is failed with error: "'500 Internal Server Error' received from 'POST https://inhouse-products:8081/rest/tenant//onLimitChange': Operation 'LIMIT_CHANGE' failed. Fulfillment Request 'PR. Reason: Your order is invalid, as it contains 2 main offer(s) " Change Service Plan failed: Task "Delivering event 'Resource limits changed' for APS application inhouse-products(https://inhouse-products:8081/rest)" (id = XX) is failed with error: "'500 Internal Server Error' received from 'POST https://inhouse-products:8081/rest/tenant///onLimitChange': Operation 'LIMIT_CHANGE' failed. Fulfillment Request 'PR'. Reason: Your order is invalid, as it contains 2 main offer(s) Cause This issue was not identified as a software issue, but it was confirmed that the issue is not reproducible on the specific version of PLM or above. Resolution Cancel the Change Order and upgrade PLM to version 1.10.660 or above. Once the upgrade is completed, place a new Change Order.

Original Publishing Date: 2023-05-24 Symptoms When I try to assign accounts to discount, and there is at least one of those accounts which is cancelled in BSS, then in case that it's already removed from OSS (APS bus), there is no data in Discount Manager. Billing > Discounts > Choose any discounts > Click "Accounts" in Discount > Assign Account: List of accounts do not load. Error "Account XXXXXXX not available." Cause Software issue with id #DM-151. Resolution Please contact your TAM to schedule an update for component discount manager to version DM-1.5.

Original Publishing Date: 2023-05-25 Symptoms PPR file has been uploaded to UX1 panel to create new Service Plans. After the import no plans are added. There is a failed task in Operations side with following error message: '500 Internal Server Error' received from 'POST https://inhouse-products:8081/rest/application/581c65a7-8d9d-4033-8708-85db2b522770/applyConfig': javax.ejb.EJBTransactionRolledbackException: Subscription Period may not be shorter than Billing Period. Cause Subscription Period is shorter than Billing Period on PPR file for this Service Plan. Example: You are trying to create a Monthly based plan, in Subscription Period you set 1 Month(s), while in Billing Period you set 1 Year(s). This means this Service Plan will be charged for an entire year even if you just purchase it for a month. This is wrong so it does not allows you to import this configuration. Resolution Align Subscription Period and Billing Period in PPR file, then try to upload it again from UX1 panel. If this solution does not work or prompts a new error, please contact CloudBlue Technical Support.