Published Solutions
-
[APS Connect] Preview of APS Connector fails: Readiness check failed. Verify that correct health check URL is provided and that it responds with status code 200.
Original Publishing Date: 2020-01-22 Symptoms Preview of APS Connector fails: "Failed to deploy backend for . Readiness check failed. Verify that correct health check URL is provided and that it responds with status code 200. Connector's standard output: \n " Cause There can be multiple reasons. Resolution Make sure that your connector backend meets all the requirements specified at http://help.aps.odin.com/publish e.g.: a. It is important that request-response (access.log style) logs must be written to STDOUT. In this case it will be easier to understand why the deployment fails and how the error can be fixed. b. Such error can be shown if connector requires more than 256Mi RAM. To check it, you may deploy connector locally (or on your kubernetes cluster) and check its memory usage via docker ps. Deploy the docker image locally and make sure that it is accessible via /connector path (all the methods need to be now under /connector/...). Detailed info about API requirements can be found here: https://help.aps.odin.com/api If you created a new version of docker image for connector backend, it is necessary to upload it with a new tag, not replace the older version with a new one. Otherwise, cached older version will be still used at APS Connect kubernetes cluster, and the preview will fail If you develop you Connector on the basis of fallball-connector, make sure that you are using the latest version mentioned in release notes: http://help.aps.odin.com/releases/. To find it click the latest release and find the version of Fallball Connector (Simulator). Internal content
-
[APS Connect] How to deal with unsupported API methods on the side of cloud service?
Original Publishing Date: 2020-01-22 Question How do I set things up to be clear that we do not support changing SKU/SKU limits? Validation is currently failing because it tries to change from L1 to L2 and we correctly return not supported: Internal error: APSC: Configuring: resource 09eca07c-d5c2-4856-9ee1-dcceb6b7887c of type 'tenant' (http://aps.odin.com/app/odinappconnectforqb/tenant/1.49) for APS application 'OdinAppConnect': not supported. Answer There is no way to prevent testing of Update Limits API during the validation https://help.aps.odin.com/api/change-limits Connector Backend must implement this method by design. You may mock this method and return 200 OK to such type of API request as a workaround. Internal content
-
How to disable recursive DNS queries
Original Publishing Date: 2020-01-22 Symptoms I would like to disable DNS recursion; the PCI compliance check fails because recursive DNS queries are allowed. Resolution To disable recursive DNS queries follow these steps: Log in to Parallels Plesk Panel as the administrator. Go to Tools and Utilities > General Settings: DNS Template > DNS Recursion tab. Switch the recursion setting to Deny and click the Set button. To allow localhost queries, follow these steps: Log in to the Plesk server as the administrator. Open the file %plesk_dir%\dns\etc\named.user.conf for editing. Set the following entry: allow-recursion {localhost; }; Restart the DNS server. If he Microsoft DNS server is used, the Deny option cannot be selected. Select Allow for local requests only, or switch the DNS server to the BIND DNS server on Tools & Settings > Server Components. WARNING: If DNS recursion is disabled, then the DNS server must not be used as the default resolver by any other server or service. Otherwise, attempts to resolve external names will fail due to disabled recursion, which may lead to problems. For example, the mail server will not be able to send mail out since all attempts to resolve MX records for external domains will fail. Internal content
-
OACI server creation fails: Cannot find suitable hardware node due to absence of IPv6 pool
Original Publishing Date: 2020-01-22 Symptoms OACI virtual environment creation fails. The following error is displayed for 'Provisioning "PACIVirtualEnvironment" for APS application Cloud Infrastructure' task in case of VPS-NG provisioniing: [ApplicationUnknownError] Provisioning: resource 2edb490c-f333-465e-b14b-fecfd47e8fa9 of type 'environments' (http://www.parallels.com/infrastructure/virtual-environment/1.0) for APS application 'Cloud Infrastructure-1.4-1951': [IM] P30002: Cannot find suitable hardware node. Please see Tasks > Cloud Infrastructure Log for details with UUID [8df56e6f-34f9-4d2a-8b2f-70697d353035]. Cause No IPv6 addresses are available in the network group, to which the servers in the used location are attached. Resolution Add IPv6 pool to the used network group or switch the network group for the servers in the location. Configuration of network groups is available at: TOP > Infrastructure > Cloud Infrastructure Network In order to change network group assignment for a hardware node: go to the node screen set is as 'Not Ready To Provide' open 'Cloud' tab press 'Change Network Group' Internal content Link on internal Article
-
Modify Exchange mailbox does not work after POA 5.5.1 upgrade on domains with Exchange 2010 Multi-Tenant
Original Publishing Date: 2020-01-22 Symptoms After upgrade to 5.5.1, modifying Exchange mailboxes, like changing limits, fails on domains with Exchange 2010 Multi-Tenant with the error below: Cannot load Windows PowerShell snap-in Microsoft.Exchange.Management.PowerShell.E2010 because of the following error: The type initializer for 'Microsoft.Exchange.Data.Directory.Globals' threw an exception. Cause .NET 4.5 installed on WPE nodes is not compatible with 5.5.1 update on domains with Exchange 2010 Multi-Tenant. Resolution Uninstall .NET 4.5 on all WPE nodes, use .NET 4.0 instead. Internal content
-
Unprovisioning tenant task for Trend Micro Security fails with 500 error
Original Publishing Date: 2020-01-22 Symptoms Unprovisioning "tenant" for APS application Trend Micro Security fails with the following error output: ErrorInternal Server Error\n The following entries could be observer in debug-enabled /var/log/httpd/error_log of Trend Micro Security on the endpoint: # touch /var/www/html/TrendMicroWFBSS/config/.debug # tail -fn0 /var/log/httpd/error_log [2018-08-01 13:43:52.912567 UTC] TRACE #Request to APS controller [apsc-request-5b61b918dec9e]: PUT https://172.16.32.41:6308//aps/2/resources/0b9d3909-a4ad-499d-93a4-30a34ad74d97/notifications/89ccc4a8-c588-47f8-86ff-b0c920e341d3 ... {"message":{"message":"Cancelling Subscription"},"details":{"message":"Trend Micro Worry Free Business Security Services"},"type":"activity","status":"inProgress"} [2018-08-01 13:43:52.953755 UTC] TRACE #Response from APS controller [apsc-request-5b61b918dec9e]: HTTP/1.1 500 Internal Server Error Cause The event notifications created by subscription were removed for some reason. Possible reasons: Customer CP version was switched from UX1 to CCPv1 and back. Another possible cause is that UX1 notification was removed by Periodic Task On-screen notifications cleaner (it could happen for old events with notifications older than 1 year). For example, Service Trend Micro Security 4.0-61 was provisioned on 1st of January, 2018. Customer got UX1 On Screen Notification about successful service provisioning. Corresponding notification will be cleaned up on 1st of January, 2019 (after 1 year). After 1st January of 2019 Trend Micro Security 4.0-61 service termination for such subscription could fail with symptoms above. Resolution The issue was found in Trend Micro Security 4.0-61 package and should be completely fixed in new package version. Contact your TAM or PTA Team to apply an internal solution. Internal content Link on internal Article
-
Azure Password reset notification email is not scheduled to be sent
Original Publishing Date: 2020-01-22 Symptoms After reset the password for Azure Admin from UX1 (reset password for Microsoft User ID) no email notification is being sent Task reset_admin_user completed successfully in Task Manager, for example: Execute operation 'reset_admin_user' with ID a7bb06bd-4565-45c6-8566-6387f9a7ee88 on resource 1cfd6c91-2dbc-4b00-8e9e-b1e9487edfe6 The issue is actual for Azure CSP application 7.x and 8.x. Cause This behavior is considered as unexpected and the Software related issue was submitted with ID #APSA-20987. Resolution Contact your Technical Account Manager or Pooled Technical Associate Team at pta@cloudblue.com to clarify the status of APSA-20987. Internal content
-
AzureCSP: Slow subdomain form loading due to the 'domain_candidates' method.
Original Publishing Date: 2020-01-22 Symptoms AzureCSP subdomain form is loading slowly - it takes ~10 seconds to appear. The following request takes the most time to complete: https://cp.provider.com/aps/2/resources/.../domain_candidates?account_id=123 Cause Software-related issue #APSA-19087: "PCP/Store: create additional subscription - slow domain candidates screen loading". Resolution Contact pta@odin.com ot TAM to trace the status of the issue. Internal content
-
Can not install Virtuozzo template: couldn't connect to host
Original Publishing Date: 2020-01-22 Symptoms A task like below fails with the "couldn't connect to host" message: Task name Install set of VZTemplates on VPS HW node Last execution output Internal error: Can not install Virtuozzo template from http:///tarballs/templates/poa-5.4-1504/pa54-mysql5-server-centos-5-x86_64-ez-20090616-1.noarch.rpm : 7 : http:///tarballs/templates/poa-5.4-1504/pa54-mysql5-server-centos-5-x86_64-ez-20090616-1.noarch.rpm : couldn't connect to host. Cause On the remote host (identified by , likely the OA core) the HTTP or FTP service(depending on the URLs in last execution in output) is not running or firewall rules are preventing the connection. Resolution Check the state of the corresponding service and make sure that no firewall rules are blocking the connection. In case the OA core was migrated recently using backup.sh and restore.sh and tasks fail with this error pointing to FTP service, please contact Odin technical support. Internal content Link on internal Article
-
APS request fails with "Allowed limit of 104857600 bytes is exceeded"
Original Publishing Date: 2020-01-22 Symptoms Request to APS application fails with the following error message in core.log on Management node: Jan 17 01:15:43.516 : DBG [aps-service:3414205 aps-service-task-16388:528469 pau]: c.p.p.s.c.e.EndpointExecutorBean endpoint call failed: javax.ws.rs.ProcessingException: com.parallels.pa.service.aps.exception.APSError: Allowed limit of 104857600 bytes is exceeded: 104858624 bytes read Cause Request fails due to platform limitation. Custom Operation call cannot return responses over 100 MB. Such limitation is implemented in order to prevent Out-Of-Memory conditions in Java on Management Node. Resolution APS application should be reworked in accordance with the platform limitation. Internal content Link on internal Article