Search Engine: Elastic

Article ID: 132407, created on Mar 19, 2018, last review on Mar 19, 2018

  • Applies to:
  • Operations Automation 7.3

Symptoms

  1. Task "Execute operation 'provisionWebsite' for Provisioning WebHosingPlesk subscription failed with error:

    There are no compatible Plesk nodes for provisioning: Nodes that do not meet the requirements
    
  2. In log /var/log/shm-dispatcher/dispatcher.log on Plesk Management Node can be found the corresponding message, for example:

    The node 192.0.2.20 does not meet the following hosting service requirements: Array
    
    [0] => Odin\ShmWebDispatcherBundle\Aps\Resource\StructureProperty Object
    (
        [name] => panel
        [class] => setting
        [type] => enum
        [value] => 17.0
    )
    
  3. WebHosting Plesk Linux Service Template is configured to use particular version of Plesk panel, e.g. 17.0.

  4. Plesk nodes were updated recently and have Plesk panel version 17.5.

Cause

By design, system automatically picks Plesk version from node only in case the parameter Any Plesk version is set in PCP > Products > Service Templates > WebHosting Plesk Linux Template > Hosting Parameters > Web hosting panel version.

In case if the particular version of Plesk panel is specified, WebHosting Plesk module relies on the value, specified in the Template, leading to error, since such version is not available on the node anymore.

Feature request PFR-1535 for improving error reporting - such as adding subscription id to the task - has been submitted.

Please contact your Technical Account Manager to check the status of the request.

Resolution

  1. In PCP > Products > Service Templates > WebHosting Plesk Linux Template > Hosting Parameters change Web hosting panel version parameter to Any Plesk version or to new updated version;
  2. In PCP > Products > Service Templates > WebHosting Plesk Linux Template > Synchronize check and synchronize the required subscriptions;
  3. Restart failed task.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF