IBM Support

IJ23465: PATCH PRETEST VALIDATE_HOSTNAME.SH CAN FAIL ON A SECONDARY MANAGED HOST APPLIANCE CAUSING PATCH PROCESS TO FAIL

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • During the QRadar patch pretest, the validate_hostname.sh
    script can fail when running on a Secondary Managed Host
    appliance in a High Availability pair causing the patch to fail.
    Messages similar to the following might be visible when this
    issue is occurring:
    [INFO](testmode) Running pretest 7/8: Validate deployment
    hostnames
    ERROR: This patch requires SSH access to all Managed Hosts to
    validate hostnames.
    ERROR: The following Managed Hosts are not accessible via SSH:
    - <appliance>
    [ERROR](testmode) Patch pretest 'Validate deployment hostnames'
    failed. (validate_hostname.sh)
    [INFO](testmode) Running pretest 8/8: Check for QIF appliances
    in deployment
    [ERROR](testmode) Failed 1/8 pretests. Aborting the patch.
    [ERROR](testmode) Failed pretests
    [ERROR](testmode) Pre Patch Testing shows a configuration
    issue. Patching this host cannot continue.
    [INFO](testmode) Set ip-135-56 status to 'Patch Test Failed'
    [ERROR](testmode) Patching can not continue
    Status Summary of Hosts
    +----------+-------------------+
    |Hostname  |Status             |
    |----------+-------------------|
    |<appliance> |Patch Test Failed  |
    |<appliance>|No Action Performed|
    +----------+-------------------+
    Patch Report for <ipaddress>, appliance type: 500
    Patch pretest 'Validate deployment hostnames' failed.
    (validate_hostname.sh)
    <aplliance>:  patch test failed.
    

Local fix

  • Contact Support for a possible workaround that might address
    this issue in some instances.
    

Problem summary

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 Fix Pack
    3 and 7.4.0 Fix Pack 1.
    

Problem conclusion

  • This issue was fixed in QRadar QRM QVM release of 7.3.3 Fix Pack
    3 and 7.4.0 Fix Pack 1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ23465

  • Reported component name

    QRADAR SOFTWARE

  • Reported component ID

    5725QRDSW

  • Reported release

    732

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-03-11

  • Closed date

    2020-04-15

  • Last modified date

    2020-04-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    QRADAR SOFTWARE

  • Fixed component ID

    5725QRDSW

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSBQAC","label":"IBM QRadar SIEM"},"Platform":[{"code":"PF025","label":"Platform Independent"}]}]

Document Information

Modified date:
16 April 2020