OS Patching Vendor Health Dashboard

Version 204
    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-09-15 10:00 PM EDT

     

    Operating SystemOS Vendor URLStatusStatus Date

    Notes

    CentOSOK2020-09-15No known issues.
    MicrosoftOK2020-09-10

    Microsoft released patches (Security and Non-security) for various products, but they are not visible after the latest TSSA Patch Catalog Update job.

    There are no error in the Catalog Update job and it finishes successfully. However, none of the patches that were released on September 8th are available in the TSSA patch catalog.

     

    BMC has raised a Critical case with Ivanti and will update the Dashboard with the updates as they are available.

     

    UPDATE: As of about Noon time EDT on Sept 9th Ivanti have resolved this problem.  TSSA Catalog Update Jobs will now receive new September patch data upon execution.

    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

     

     

    OR

     

     

    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

    https://content.ivanti.com/

     

    Recent Change

    OK

     

     

     

     

     

     

     

    ---------

    OK

    2020-01-08

     

     

     

     

     

     

     

     

     

    ---------------

    2019-07-17

    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

    http://content.ivanti.com/data/partner/manifest/partner.manifest.xml

     

     

    The URL has changed to

    https://content.ivanti.com/data/oem/BMC-Bladelogic/data/93/manifest/partner.manifest.xml

     

    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

     

     

    ------------------------------------------------------------------------------------

     

     

    Problem:

    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.

    .

    HP HP-UXOK2020-09-15No known issues.
    IBM AIXOK2020-09-15No known issues.
    Oracle Enterprise Linux (OEL)OK2020-09-15No known issues.
    Oracle SolarisOK2020-09-15No known issues.
    SuSE LinuxOK2020-09-15No known issues.
    UbuntuOK2020-09-15No known issues.
    Redhat 8 OKOK
    2020-06-04

    Redhat 8 Patch Catalog Update job in TSSA Fails with the following error in Job run log :

     

    Validation Error :- BLPAT1212 - Failed to run reposync on repo directory

    Possible remediation steps :- For more details, please check the yum_metadata_generator.log file generated in repository location.

    The channel name is 'rhel-8-for-x86_64-baseos-rpms'.

     

    Following errors could be seen in the yum_metadata_generator.log on the Patch Repository server under the Repository location :

     

    [MIRROR] cryptsetup-reencrypt-2.2.0-2.el8.x86_64.rpm: Status code: 404 for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/baseos/os/Packages/c/cryptsetup-reencrypt-2.2.0-2.el8.x86_64.rpm (IP: 23.64.4.251)

    [MIRROR] cryptsetup-reencrypt-2.2.0-2.el8.x86_64.rpm: Status code: 404 for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/baseos/os/Packages/c/cryptsetup-reencrypt-2.2.0-2.el8.x86_64.rpm (IP: 23.64.4.251)

    [MIRROR] cryptsetup-reencrypt-2.2.0-2.el8.x86_64.rpm: Status code: 404 for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/baseos/os/Packages/c/cryptsetup-reencrypt-2.2.0-2.el8.x86_64.rpm (IP: 23.64.4.251)

    [MIRROR] cryptsetup-reencrypt-2.2.0-2.el8.x86_64.rpm: Status code: 404 for https://cdn.redhat.com/content/dist/rhel8/8/x86_64/baseos/os/Packages/c/cryptsetup-reencrypt-2.2.0-2.el8.x86_64.rpm (IP: 23.64.4.251)

     

    This is due to some issues accessing these URLs at Redhat. BMC has raised a case with Redhat and they are working internally to fix this.

    There is no ETA so far.

     

    The problem is related to specific patches and its possible and if those patches are already downloaded in a previous run the catalog update job will be successful.

     

    The problem is resolved on June 10th.