Original Publishing Date: 2022-12-02 Symptoms Customer is using external mail relay server without authentication. Checking the configuration on bss-scheduler pod  /usr/local/bm/conf/AMAIL-users.db: [root@bss-scheduler-5d945b87c4-qptvk /]# cat /usr/local/bm/conf/AMAIL-users.db [Server] Host = 123.123.123.123 Port = 25 Under Billing > System > Log > Outgoing E-Mail Log there are a lot of Outgoing E-Mails are in failed state with error: mailsmtp_rcpt(example@cloudblue.com) failed with code error 1:'Unexpected error code' The relay SMTP server is responding with unexpected error on RCPT stage. To confirm what is the exact error following commands can be executed on the bss-scheduler pod one by one: 1) telnet 123.123.123.123 25 2) EHLO bss-scheduler-859cb54f4d-prlvq 3) MAIL FROM: noreply@cloudblue.com 4) RCPT TO: example@cloudblue.com Resulting a response similar to this:  454 4.7.1 : Relay access denied Cause Incorrect SMTP server configuration. Server doesn't allow to send your email to that domain.  Resolution Please check documentation for your smtp server and configure it properly.

Original Publishing Date: 2022-12-27 Symptoms Several task (Report microservice usage data, Report usage data) that sent usage data to report.cloudble.com/post failed with error below in task log: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target unable to find valid certification path to requested target The same error could be seen in /var/log/pa/core.log: 2022-12-27 15:03:56,933 INFO [task:12097112:108087 Thread-1059-(ActiveMQ-client-global-threads):31017 pau]: c.p.p.s.s.e.SenderBean Publishing usage report to https://report.cloudblue.com/post 2022-12-27 15:03:57,328 ERROR [task:12097112:108087 Thread-1059-(ActiveMQ-client-global-threads):31017 pau]: c.p.p.tracer exit by exception: com.parallels.pa.service.statistics.ejb.SenderBean.send correlationId task:12097112:108087 javax.ejb.EJBException: Report to https://report.cloudblue.com/post failed: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at deployment.core-ear.ear.statistics-ejb.jar//com.parallels.pa.service.statistics.ejb.SenderBean.send(SenderBean.java:159)     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Cause Certificate has been changed on report.cloudblue.com and resulted with PKIX error. This issue has been recognized as software issue #BID-1668. Resolution The certificate has been reverted back to the original one before the error. Please resubmit the failed task, and it should be completed without issue. To further track the status of this bug, please contact your TAM.

Original Publishing Date: 2022-12-31 Symptoms FEA_NCE_PROMO is configured in the platform but the promotion is not showing up on the checkout screen. More information about configuring promotions for Microsoft 365 NCE plans can be checked at the following link: CloudBlue Commerce 21 Promotions for Microsoft 365 NCE Plans. Cause FEA_NCE_PROMO features are unavailable at the moment, they would be implemented in the scope of PFR-5497.  Resolution Please, reach out to your TAM in order to get the PFR status.

Original Publishing Date: 2023-01-02 Symptoms Alert re_adapter_bill are frequently fired by Prometheus to Zabbix. On Zabbix web frontend problems section, the triggered problems has a fixed trend to it. Example: Cause According to CloudBlue 21.x official documentation, this alert will appear due time taken to for order calculation is more than 5 seconds. The 5 seconds threshold in the Prometheus alert rule is too low. Resolution Increase the Prometheus alert rule re_adapter_bill treshold to a higher and acceptable value for the environment by following this KCS article: How to increase threshold for re_adapter_bill and re_adapter_rate alerts in Prometheus. Internal

Original Publishing Date: 2023-01-11 Right after the upgrade of OSS component to version 21.9, you need to take the following steps. On a computer with access to Kubernetes cluster where your CloudBlue Commerce installation is deployed, enter to the OSS pod. Below is the example of a command to do that: kubectl -n NAMESPACE exec -ti oss-node-0 bash Run the following command on the pod: # python >>> from poaupdater import openapi >>> api=openapi.OpenAPI() >>> api.pem.APS.addBrandingTemplateGroups() Wait for the operation to complete. Time required to complete the operation directly depends on the number of resellers on the installation.

Original Publishing Date: 2023-01-13 Symptoms In same cases there exits a discrepancy between the BSS version deployed and the BSS application showing in UI. For example, checking with helm we see the latest version installed, in this case bss-21.8-406: # /usr/local/bin/helm -n list NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION bss prod-cbc 4 2022-12-28 19:21:10.820038819 +0000 UTC deployed bss-21.8.406 In this case, the command used to upgrade the componet was: # setup-product.sh -s helmfile-deploy -n -c bss -c oss But from provider CP we still see one the previous versions installed: Cause This happens because helmfile-deploy will upgrade bss-war only if in config.yaml file is set specifically: components: bss: version: 21.8.406 This issue has been recognized as a Software issue with id OA-32913. Resolution This issue can be work around by following this procedure to update the components: 1. upgrade bss and branding-ui charts with the following command: # setup-product.sh -n -s helmfile-deploy -c bss -c branding-ui-cluster 2. extract the config.yaml file from the secret: # kubectl get secret helmfile-deploy -n -o "jsonpath={.data['config\.yaml']}" | base64 -d > config-test.yaml 3. write inside the config-test.yaml the bss.version: 21.x.x(installed in p1 version) and save. 4. upgrade oss with the following command: # setup-product.sh -n -f config-test.yaml -c oss

Original Publishing Date: 2023-01-24 Symptoms Go to a reseller UX1 > Marketplace > Click on a tile > the page returns "No plans available" error. Example: Replicating this issue with browser inspect element, shows the request for listing all service plans available for purchase for a reseller has error as below: { "error": "com.parallels.bss.rest.errors.BSSAPSError", "packageId": "98a94bf3-593d-43d2-85f7-efe252f4700b", "message": "javax.persistence.NoResultException: No entity found for query", "http_request": "GET https://127.0.0.1:8081/pa/billing/73e70ea5-ece5-498b-a20b-942c3f959f6d/pc/plans-for-buy-and-resell?planRequest=BUY_RESELL" } Cause This is due to reseller subscription based on a Reseller Service Plan is unexpectedly in state Terminated and Stopped as it was not autorenewed due to the fact that the Reseller Service Plan which the subscription is based on has Autorenewal set to Disabled. Resolution Restore the Terminated and Stopped reseller subscription by manually renewing it. Internal

Original Publishing Date: 2023-01-20 Symptoms Scheduled orders are not showing as processed in Commerce even when they have gone through Connect. Also, the status in Commerce is 'Activation is scheduled'. Status in Commerce: Status in Connect is Approved or Scheduled: Cause If the order is placed after the RN date, the order will be in 'Activation is scheduled' until the next month's BO. There is more information in the following link: https://docs.cloudblue.com/cbc/21.0/Billing-Providers-Guide/Scheduled-subscription-changes.htm In Connect, scheduled orders can be active or scheduled while awaiting for the Requested Activation date. When the PR is placed it is in Scheduled status, but on the Renewal Date (check Connect > Subscription > Billing) it became active.  It is possible that a Requested Activation date is prior RN date, but the connector will schedule the request until the day before the renewal date. Resolution The order will be processed in Commerce on the next BO date.

Original Publishing Date: 2023-01-31 Symptoms Partial upgrade requests to an existing subscription could stuck in the IN_PROGRESS_NONE_LO_NONE status. Cause The reason causing this issue can be one of these: There is another change order for that subscription that is not yet completed. The subscription that is being upsized was created during a partial upgrade to a new subscription less than 24 hours ago. Resolution To resolve this issue, you need to cancel the stuck partial upgrade requests. To do this, complete the following steps: Cancel the request related to the stuck partial upgrade request in Connect. After this, the related change order status in CloudBlue Commerce will change from Long running operation to Failed provisioning and the partial upgrade request status will change to PROBLEM_NONE_PF_NONE.  After that, cancel the change order. Depending on the reason that caused the issue, place the change request after: The existing change order for the subscription is completed. 24 hours passed after the creation of the upsized subscription.

Original Publishing Date: 2023-02-03 Symptoms From UX1 for reseller with New Experience activated is not possible to place and order. It stops and spins after step "Reseller Options".  No related errors in browser dev tools nor in the pod logs. Cause Issue is cause by software related issue with ID OA-32441 'Can't proceed to the last step of sales wizard'. Resolution Reseller needs to switch to the old experience to fulfill the order. To do that, go to UX1 panel for reseller and just click on the upper right  button 'New Experience' to deactivate it.  Further instructions on how to switch on and of the new experience for UX1 can be found in the link: https://docs.cloudblue.com/cbc/21.0/UX1-for-Resellers-Provider-Guide/How-to-Enable-New-Experience-in-UX1.htm?Highlight=new%20experience The issue  has been fixed in version of the component UI and Branding 21.9.184.