Viewing Patching Job results

On completion of a Patching Job, results are shown in the content editor in the upper-right section of the screen. In addition to the initial Analysis Run results, remediation results from all subsequent remediation runs are displayed as well.

The following procedures describe how to view Patching Job analysis and remediation results:

Note

All remediation runs of a Patching Job run are displayed, regardless of whether remediation was invoked automatically (based on the Create remediation artifacts setting) or manually (using the Deploy Selected Patches option or the Remediate All Servers option, as described in Managing-patches-through-the-analysis-results-view).

(Solaris and Linux only) If the Analysis Job is set to Debug mode on the application server level, the Analysis logs are included in the Appserver logs. The Analysis logs specify the location on the target in which the results and the error logs of the Analysis are stored.

To view Patching Job analysis results

  1. Right-click the Patching Job and select Show Results.
    The name of the Patching Job, as defined during job creation, is displayed as the root node in the hierarchical tree. All runs of the Patching Job and their results are displayed beneath the root node.
  2. Select the root job node to display additional information in column form on the right. The following information is displayed:
    • date and time of each job run
    • type of job run
    • final status of the job
    • starting and ending date/time for the job

    • user that ran the job

      Note

      For a description of menu options available from the root job node, see Managing Jobs.

  3. Expand the root node.
    A list of run dates and times for the Patching Job is displayed.
  4. Expand one of the job run nodes.
    Analysis and remediation results are displayed on separate lines.
  5. Select the analysis results node. 
    Patching Job Analysis statistics are displayed on the right side in column format including what was discovered missing, installed (for Windows and Red Hat Enterprise Linux only), how many target servers were scanned, and how many target servers were not scanned.
  6. Expand the analysis results node to display the Object and Server Views.
    • Object View — This view lists every missing patch discovered during analysis together with architecture, whether the patch is recommended by the vendor site, description of the patch, and so on.
      (For Windows and Red Hat Enterprise Linux only) You can also view the list of installed and missing patches and RPMs and Erratas under the Installed and Missing nodes. You can exclude patches from servers by using the Object View. For more information about excluding patches, see Managing-patches-through-the-analysis-results-view .

    • Server View — Server View organizes target servers included in the job according to these subcategories:

      • Failed Targets - Displays the targets where the Patch Analysis Job failed.
      • Warning Targets - Displays the targets where the Patch Analysis Job run was completed with some observations. For example, a target for which reboot is pending.
      • Successful Targets - Displays the targets where the Patch Analysis Job ran successfully.

      Target servers are displayed on pages. The number of servers on each page can be configured (Window > Preferences > Paging Options > Page Size (see Customizing-preferences  for more details). Target servers are listed individually including final status as well as the installed (for Windows and Red Hat Enterprise only) and missing number of:

      • Microsoft Windows: bulletins and hotfixes
      • Solaris: clusters and patches
      • AIX: containers and filesets
        Examples of containers: Technology Level, Service Pack, APAR ID, PTF, Critical Fix, Security Fix, or Latest Fix
      • Red Hat Enterprise Linux: RPMs and Erratas
      • SUSE Linux Enterprise and Oracle Enterprise Linux: RPMs
      • CentOS: RPMs 
      • OL ULN: RPMs and Erratas 

      Important (Applicable for Red Hat Enterprise Linux only)

      Starting version 23.1, data (including count) for the installed RPMs and Erratas for a target server node is populated in the Server Automation database. The installed count is calculated based on the analysis options selected in the patch catalog, excluding the patches specified in the patch exclude list.

      For a fresh installation of version 23.1, by default, the Installed RPMs and Installed Erratas columns appear on the Server Automation Console and display the installed RPM or Errata count. 

      After you upgrade to 23.1, to populate the data for the installed RPMs and Erratas, you need to run the Patching Job again. To display the Installed RPMs and Installed Erratas columns on the console, delete the dialog_setting.xml file from the %AppData%\Roaming\BladeLogic\BladeLogic\1_2_1\Workspace1\.metadata\.plugins\com.bladelogic.client.ui directory on the host where the TrueSight Server Automation console is installed and open the console again. Note that if you had done any customizations in the dialog_setting.xml file before deleting it, you need to do them again.

      If you have selected the Security Mode option for patch analysis, a target server node shows only the installed security patches on the target server. Any patch whose current version is not a security fix is not displayed as the installed patch. For example, consider a patch with versions 1, 2 and 3, where version 1 is currently installed, version 2 is a security fix, and version 3 is a general bug fix. In such a case, if you deploy version 2 as part of remediation, in next analysis, version 2 will be shown as installed. If you deploy version 3, it will not be shown as installed because it is not a security patch.

To further manage the listed patches and to exclude patches through the analysis results view, see Managing-patches-through-the-analysis-results-view.

To view Patching Job remediation results

  1. Right-click the Patching Job and select Show Results.
    The name of the Patching Job, as defined during job creation, is displayed as the root node in the hierarchical tree. All runs of the Patching Job and their results are displayed beneath the root node.

  2. Select the root job node to display additional information in column form on the right.
    The following information is displayed: date and time of each job run, the type of job run, the final status of the job, the starting and ending date/time for the job, and the user that ran the job.

    Note

    For a description of menu options available from the root job node, see Managing Jobs.

  3. Expand the root node.
    A list of run dates and times for the Patching Job is displayed.
  4. Expand one of the job run nodes.
    Analysis and remediation results are displayed on separate lines. All remediation runs of a Patching Job run are displayed (each as a separate node), regardless of whether remediation was invoked automatically or manually.

  5. Expand the remediation results node with the relevant date and time.
    Nodes are displayed for the download run and for remediation run.

    • Remediation run node displays the following details:
      • All Targets: Displays all targets under that remediation job irrespective of the deploy status.
      • Failed Targets: Displays targets on which all or some of the patches are not successfully deployed.
      • Not Started: Displays targets on which deployment has not been started.
      • Pending Reboot Targets: Displays targets for which the reboot is pending (after successfully deploying all patches). The reboot is not initiated by the Deploy Job and must be initiated manually. If you want the Deploy Job to automatically reboot servers that require a reboot, make sure to set the single-job mode option as described in Specifying-job-options.  
      • Pending Targets: Displays targets on which deployment is completed up to the stage or simulate phase.
      • Running Targets: Displays targets on which the patches are currently being deployed.
      • Successful Targets: Displays targets on which all patches have been successfully deployed without any warnings.
      • Successful With Warnings Targets: Displays targets on which all patches have been deployed successfully with warnings.
    • Download run node displays the Object View, which lists the patches that are downloaded successfully.

    Note

    If a Batch Job is run as part of the remediation, the Batch Job run is not displayed. To view results for such a Batch Job, follow the instructions in Viewing-Batch-Job-results-for-remediation.

To view the status of Deploy Jobs

A typical scenario for administrators is the need to provision, patch, and run compliance on their servers in sequence, so that they can make the compliance results and the compliant servers available to their business unit. However, if they lack accurate information about whether or not the Patching Job completed (and about when it completed, if it did complete), administrators cannot schedule the Compliance Job correctly.

Deploy Jobs are chained to the parent Patching Job, and the parent Patching Job is marked as complete only after the Deploy Job finishes execution. Consequently, any jobs that are scheduled to run after the Patching Job start only after the Deploy Job finishes execution.

The TrueSight Server Automation Console displays the corresponding Batch Job Run status with the Batch prefix under the Remediation Run node. The Batch Job Run lists the execution status of the Deploy Job or Jobs included in it, as shown in the following figure. 

g_V95_enhancedPatchingJobsStatusView.gif

Where to go from here

Remediating-servers

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*