OS Patching Vendor Health Dashboard

Version 178
    Share:|

         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.

     

    Status as of 2019-05-15 14:45 EST

     

    Operating SystemOS Vendor URLStatusStatus Date

    Notes

    Microsoft WindowsError2019-05-15

    Problem

    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 :

     

    https://forums.ivanti.com/s/article/Oracle-SE-Java-8-support-changes-and-how-it-effects-deployments-through-Ivanti-Patch-Management-solutions

     

    BMC is working to resolve the issue

     

    PS - While the issue being worked on by BMC, Please remove the 'Sun Java' filter from the Catalog as a temporary workaround, doing this the download of Java Patches will not be done and the Catalog Update job will be successful.

    Microsoft Windows

    https://content.ivanti.com/

     

    old-URL

    http://x**.shavlik.com/

    Warning
    2019-02-21

    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…

     

    2019-02-25  - *** Advanced Warning ****

    Ivanti/Shavlik is moving the legacy website at xml.shavlik.com to a new provider on February 25th.

    No outage is expected at this time but a disruption is possible. The DNS entry for the URL will be redirected to the new provider.  Note this only affects the legacy URL's at xml.shavlik.com.

    Note: if you are using the legacy URL's you may need to restart your appserver to pickup the new IP for the DNS name.

     


    2018-03-07

    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.

     

    2018-01-19

    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.
    Redhat LinuxError2019-03-07

    Update March 13 2019 10:15 EST

    BMC has begun rolling out hotfixed jar files to customers who have created a support case. If you have encountered this issue not not yet created a support case, please do so and provide the following details:

     

    a) Specify your exact BSA/TSSA version and build number

    b) Specify the OS of your Appserver and/or Redhat Downloader Server(Offline)

    c) Specify whether you are using online or offline patch catalogs

    d) Attach the support-files-1.0-SNAPSHOT.jar file from the following location to the case - the fix will likely involve updating this jar file.

     

    Online Patch Catalogs: NSH/br/stdlib/support-files-1.0-SNAPSHOT.jar file from one of your BSA/TSSA appservers -

    Offline Patch Catalogs: <offlineDownloaderDir>/libs/support-files-1.0-SNAPSHOT.jar

     

     

    ________________________________________________________________________________

    Update March 11 2019 17:40 EST

    During Hotfix testing on Monday 03/11, a few issues were found in handling the Redhat directory structure changes. These have been corrected and testing continues.

    Once testing is complete BMC will start rolling out the updated jar files to customers who have reported this issue. A further ETA will be provided on Tuesday March 12th.

    ________________________________________________________________________________

    Update March 8 2019 17:05 EST

    The hotfixed yum_metadata_generator.sh script continues to undergo testing by BMC Software.

    Testing involves repeatedly running RH Catalog Update Jobs and ensuring the downloaded files and directories, with the new directory structure, are processed correctly. An updated ETA will be provided on Monday March 11th based on testing results.

    ________________________________________________________________________________

     

    Update March 7 2019 14:55 EST

    The root cause of the problem is a change in the directory structure used to store rpms on cdn.redhat.com to include a subdirectory under Packages corresponding to the first letter of the rpm filename e.g.

     

    Old: https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/Packages/java-1.8.0-openjdk-1.8.0.201.b09-2.el7_6.i6…

    New: https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/Packages/j/java-1.8.0-openjdk-1.8.0.201.b09-2.el7_6.…

     

    The downloading of the rpms to the repository continues to work correctly but this change in the directory structure breaks the logic used to process the downloaded rpms.

    BMC is currently working on a fix to handle the new directory structure. If you encounter this issue:

     

    a) Open a case with BMC Software Customer Support

    b) Specify your exact BSA/TSSA version and build number

    c) Specify whether you are using online or offline patch catalogs

    d) Attach the support-files-1.0-SNAPSHOT.jar file from the following location to the case - the fix will likely involve updating this jar file.

     

    Online Patch Catalogs: NSH/br/stdlib/support-files-1.0-SNAPSHOT.jar file from one of your BSA/TSSA appservers -

    Offline Patch Catalogs: <offlineDownloaderDir>/libs/support-files-1.0-SNAPSHOT.jar

    ________________________________________________________________________________

     

    Update March 7 2019 09:30 EST Customers have reported receiving the following errors during Redhat Patch Catalog Updates. The errors are not restricted to any specific RPM

     

    Download of Package failed Rpm download failed: java-1.8.0-openjdk-headless-1.8.0.201.b09-2.el7_6.x86_64.rpm,Error occurred while downloading the patch, retries completed. (Caused By: Error occurred while connecting to url: https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/Packages/j/java-1.8.0-openjdk-headless-1.8.0.201.b09-2.el7_6.x86_64.rpm. Please verify Internet connectivity and if you have provided Proxy then verify your Proxy settings (Caused By: sun.security.validator.ValidatorException: PKIX path building failed: java.security.cert.CertPathBuilderException: Could not build a validated path. (Caused By: PKIX path building failed: java.security.cert.CertPathBuilderException: Could not build a validated path. (Caused By: Could not build a validated path.))))

     

    BMC has opened a case with Redhat Customer Support to assist.

    This page will be updated during the day on March 7th as more details are available.

     

    We will publish further details as they become available.

    SuSE LinuxOK2019-03-07No known issues.
    HP HP-UXOK2019-03-07No known issues.