Symptoms

The task "Synchronize PPM mirror on host testhost.hosting.tld" fails with multiple errors:

Last execution output   
Following packages failed to synchronize: sc-Win32-5.2-i386-RequestTracker-5.1.0.0.tgz(60):     Destination host 'testhost.hosting.com' (#1), IP '<MN_IP>' : Internal error: Cannot fetch 'sc-Win32-5.2-i386-RequestTracker-5.1.0.0.tgz': 'http://<MN_IP>/tarballs/RHEL/5/x86_64/YUM/sc-Win32-5.2-i386-RequestTracker-5.1.0.0.tgz: The requested URL returned error: 404
http://<MN_IP>/tarballs/RHEL/5/i386/YUM/sc-Win32-5.2-i386-RequestTracker-5.1.0.0.tgz: The requested URL returned error: 404
http://<MN_IP>/tarballs/RHES/4/x86_64/YUM/sc-Win32-5.2-i386-RequestTracker-5.1.0.0.tgz: The 

Cause

This is caused by POA-37576 - "PPM mirrors synchronization problems"

Resolution

If there is only one PPM mirror in Parallels Operations Automation (POA) and it is located on the POA Management node, ignore the task and do not use synchronization in the future. This functionality is overlapped by the updates/upgrades installation mechanism.

During the installation of updates, PPM packages (tgz files) are extracted from the distributed files and placed into the directory /usr/local/pem/install/tarballs/ on the POA Management Node. As a result, the contents of the PPM mirror http://<MN_IP>/tarballs is updated whenever an installation is carried out.

If you would like to fix the task:

  1. Create a temporary directory in /usr/local/pem/install/tarballs:

    # mkdir /usr/local/pem/install/tarballs/tmp_ppm/
    
  2. Copy the files from tarballs to this directory:

    # cp /usr/local/pem/install/tarballs/*tgz /usr/local/pem/install/tarballs/tmp_ppm/
    
  3. Add the URL http://<MN_IP>/tarballs/tmp_ppm to Infrastructure > Package Repository > URLs

  4. Re-run the failed task.

To get more details on bug POA-37576, contact your Account Manager.

Internal content

Link on internal Article