OS Patching Vendor Health Dashboard

Version 194
    Share This:

         BMC Customers using Automation for Patching use cases depend on OS vendors for Patches and metadata.  This document tracks the service status of the different OS Vendors as known to BMC Support.  If you have questions or concerns, please contact your support specialist.


    Note:  Microsoft has released new Servicing Stack Updates for November 2019.  These may need to be installed before other necessary updates are visible.


    Status as of 2020-01-08 10:00 ET


    Operating SystemOS Vendor URLStatusStatus Date


    Redhat Linuxhttps://status.redhat.com/.OK2019-09-18

    As per Redhat official statement on https://status.redhat.com/



    "We have identified issues that may impact downloading files, due to a problem with our content delivery network. We are investigating with our CDN vendor until the issue is resolved."




    BSA/TSSA Redhat patch catalog update may fail due to following errors due to this :




    Catalog is failing due to HTTPS Error 404 network issue.

    Please find the error log below:

    yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from rhel-x86_64-server-5: [Errno 256] No more mirrors to try.

    https://cdn.redhat.com/content/dist/rhel/server/5/5Server/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found






    https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/ceph-installer/1.3/os/repodata/repomd.xml: [Errno 12] Timeout on https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/ceph-installer/1.3/os/repodata/repomd.xml: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')



    As a possible fix has been already been applied its possible that the issue is resolved by now, please subscribe to https://status.redhat.com/ for Live Updates on this issue.


    Below is the latest from Redhat on this issue :


    CDN is currently facing the issues with few of the repositories hosted at Akamai.


    The issue is still fluctuating and largely unpredictable, You can attempt your transactions again, but they may still be met with timeouts or other errors We are already working with our Internal Teams to get it resolved at earliest possible.




    PS - This is not a BSA/TSSA problem, patch dowloads will fail outside to TSSA/BSA due to this error as well.

    Microsoft Windows

    Recent Change























    Problem.  Catalog Update fails with (is resolved)

    Error 01/08/2020 09:28:47 Validation Error :- BLPAT1004 - Http Url is not accessible.

    Possible remediation steps :- Please check the proxy login credentials

    Please check network access to vendor url




    The URL has changed to



    This can be changed in Patch Global Configuration in the Shavlik URL Configuration Tab. For the Offline Downloader, change the url in the resources\patch-psu.properties file in the offline downloader directory.


    As of 2020-01-09 17:00 EST: The http://content.ivanti.com/data/partner/manifest/partner.manifest.xml has been restored, however, customers should still update the Patch Global  Configuration with the new url: https://content.ivanti.com/data/oem/BMC-Bladelogic/data/93/manifest/partner.manifest.xml







    Windows Patch Analysis jobs in TSSA failing with the following error:


    STDERR: Error: Encountered error 0x800710dd initializing scanner - The operation identifier is not valid.Possible cause is: Signature verification certificates may not have been installed on this server. Re-run the patching job in debug mode and check log file AnalysisTrace.log for further details. Error: Unable to initialize analysis engine.Error: Analysis failed.


    As of 2019-07-17 14:20 EST:  Ivanti has published updated metadata files that do not experience this issue. Affected users should Run a new Catalog Update Job.  This should fix the issue.

    NOTE:  Users using offline catalogs should run the offline downloader again before running the Catalog Update Job.


    Microsoft WindowsOK2019-05-15


    Windows Catalog update job fails to download Java patches, following error is seen in the job run logs :


    Error while downloading payload for hotfix : jre-8u211-windows-x64.exe-JAVA8-211-en-JAVA RUNTIME ENVIRONMENT 8.0 X64-Gold, ,Error: com.bmc.sa.patchfeed.FeedException: Maximum retries completed. Failed to download https://download.oracle.com/otn/java/jdk/8u211-b12/478a62b7d4e34b78b671c754eaaf38ab/jre-8u211-windows-x64.exe.Invalid credentials. Cannot connect to url: https://download.oracle.com/otn/java/jdk/8u211-b12/478a62b7d4e34b78b671c754eaaf38ab/jre-8u211-windows-x64.exe (Caused By: Maximum retries completed. Failed to download https://download.oracle.com/otn/java/jdk/8u211-b12/478a62b7d4e34b78b671c754eaaf38ab/jre-8u211-windows-x64.exe.Invalid credentials. Cannot connect to url: https://download.oracle.com/otn/java/jdk/8u211-b12/478a62b7d4e34b78b671c754eaaf38ab/jre-8u211-windows-x64.exe (Caused By: Invalid credentials. Cannot connect to url: https://download.oracle.com/otn/java/jdk


    Reason :

    Oracle has changed the way Java updates are hosted, so they are no longer automatically downloadable. 

    Oracle now require manually accepting their licensing agreement to be able to download which generates a user token that is appended to the download URL, which means there is no single URL we can point to for those downloads. 

    Refer the URL below for more information :




    Latest releases and hotfixes mark this as a warning and state that the patch payload must be obtained directly from the vendor and copied to manually to the repository directory. Note: going forward whenever a vendor decides to put a login or paywall in place before allowing direct download of a patch a similar warning will appear and the patch will need to be obtained separately.

    Microsoft Windows






    2019-03-07 Reminder of EOL for Shavlik 9.1 SDK in September 2019. BSA/TSSA upgrade, including RSCD Agent on Windows Servers which are targets of BSA/TSSA Patch Analysis, is required to 8.9.03 or greater.


    Notification of action needed for users of TrueSight Server Automation Microsoft Windows Patching - Documentation for Tr…



    Some Microsoft Patch Rollups starting in January 2018 (including ones containing Meltdown and Spectre fixes) are not being detected during BMC BladeLogic Server Automation (BSA) Windows Patch Analysis even though the patches are not installed on the Target Server.  Note: Going forward any Cumulative Rollups will contain these patches and thus will also be dependent of the QualityCompat registry key being in place to allow detection. See KA 000147164 for more info.



    If you are seeing patches for Bulletins beginning with  "IVA18-" in your patch analysis please see the following important link:  Mystery Patches for Bulletins IVA18-XXX. .  These should be excluded from patching.



    Get latest Windows Filter Configuration File here.

    Oracle SolarisOK2014-10-30No known issues.
    IBM AIXOK2014-10-30No known issues.
    SuSE LinuxOK2019-03-07No known issues.
    HP HP-UXOK2019-03-07No known issues.