"check_patches" reports error, should I be concerned ?

[Jerry L. Sims]

Hello HP,
*******************************
HP-UX B.11.11 9000/800/N4000-75
*******************************

When I executed "check_patches" the /tmp/check_patches.report"
reported the following error :

============================== Invalid Patches
===============================

* Determining if any HP-UX 11.11 patches are missing the SD-UX
patch
* attributes required for SD-UX to handle the patches properly.
If the
* patch attributes are missing SD-UX does not treat the software
as
* patches, which can lead to unexpected results.

ERROR: One or more HP-UX 11.11 patches were not installed with
the
SD-UX patch attributes. This usually occurs when HP-UX
11.11
patches are handled by the swcopy(1M) command on an
HP-UX 10.X system, which does not recognize these
attributes,
and the patch attributes are lost. The absence of these
patch attributes will cause SD-UX on HP-UX 11.11 to
treat
these patches inappropriately.

Due to the severity of this issue, it is recommended
that the
software affected by these patches be reloaded. Once
the
software has been reloaded, the patches should be
reapplied
from a known good source insuring that the swinstall(1M)
'patch_match_target=true' option is used.

The following HP-UX 11.11 patches are missing the SD-UX
patch
attributes:

PHSS_28610 N4000/rp7400 43.22 PDC Firmware
Patch

***********************************************************
it-hp36 [/tmp]# swlist -l product | grep -i 28610
PHSS_28610 1.0 N4000/rp7400 43.22 PDC
Firmware Patch
it-hp36 [/tmp]# swlist -l fileset -a state | grep -i 28610
# PHSS_28610
PHSS_28610.KERN-RUN configured
***********************************************************
Info from "swagent.log"

======= 02/03/04 14:34:38 PST BEGIN install AGENT SESSION
(pid=19633)

* Agent session started for user "root@it-
hp36.peoplesoft.com".
(pid=19633)

* Beginning Analysis Phase.
* Source:
it-hp36.peoplesoft.com:/software/PDC_FIRMWARE.43.22
* Target: it-hp36:/
* Target logfile: it-hp36:/var/adm/sw/swagent.log
* Reading source for product information.
* Reading source for file information.

* Executing preDSA command.
NOTE: The used disk space on filesystem "/usr" is estimated to
increase by 2160 Kbytes.
This will leave 1458656 Kbytes of available user disk
space
after the installation.
NOTE: The used disk space on filesystem "/var" is estimated to
increase by 24 Kbytes.
This will leave 4139368 Kbytes of available user disk
space
after the installation.

* Summary of Analysis Phase:
* 1 of 1 filesets had no Errors or Warnings.
* The Analysis Phase succeeded.


* Beginning the Install Execution Phase.
* Filesets: 1
* Files: 3
* Kbytes: 2150
* Installing bundle "BUNDLE,r=B.." because it is
a "reference"
bundle and one or more of its contained filesets is
being
installed.
* Installing fileset "PHSS_28610.KERN-RUN,r=1.0" (1 of 1).
* Running install clean
command /usr/lbin/sw/install_clean.
NOTE: tlinstall is searching filesystem - please be patient
NOTE: Successfully completed
* Building the software file "/var/adm/sw/needs_config"
to be
used for post-reboot "swconfig" execution. The
information in
this file will be used as input to "swconfig" after the
system
reboots.

* Summary of Execution Phase:
* 1 of 1 filesets had no Errors or Warnings.
* The Execution Phase succeeded.

NOTE: Because software requiring a system reboot has been
installed,
the system will now be rebooted.
NOTE: The system must be configured after it is rebooted. If
the
"swconfig" command does not succeed during the startup
process, you may run the "swconfig" command manually
after the system boots successfully.

======= 02/03/04 14:37:53 PST END install AGENT SESSION
(Rebooting
System) (pid=19633)


======= 02/03/04 15:08:25 PST BEGIN configure AGENT SESSION
(pid=617)
(jobid=it-hp36-0029)

* Agent session started for user "root@it-
hp36.peoplesoft.com".
(pid=617)

* Beginning Analysis Phase.
* Target: it-hp36:/
* Target logfile: it-hp36:/var/adm/sw/swagent.log
* Reading source for file information.
NOTE: The filesystems in the filesystem table will not be
checked
against those currently mounted because the
"mount_all_filesystems" option is set to "false".

* Summary of Analysis Phase:
* 1 of 1 filesets had no Errors or Warnings.
* The Analysis Phase succeeded.


* Beginning the Configure Execution Phase.
* Filesets: 1
* Running config clean command /usr/lbin/sw/config_clean.

* Summary of Execution Phase:
* 1 of 1 filesets had no Errors or Warnings.
* The Execution Phase succeeded.
********************************************************
*** Callback comment ***

[Mel Burslan]

as far as I can see from the patch database, this is a firmware patch and if it went in fine and your system came back up after the reboot, I would not worry about it. All swcheck is complaining is a patch database inconsistency. As a matter of fact, re-installing this patch (i.e. re-updating the firmware) with the same firmware revision may have some unexpected (read as : nasty) effects.

Personally, I would not do it.

[Steven E. Protter]

Concerned: Yes.

Reinstall a firmware patch: No.

Open a software case with HP to clear up the consistency problem in the sd-ux database: Yes.

I echo the first responses concerns with regards to running the firmware upgade again.

SEP

[Jerry L. Sims]

Thanks for the response.

I was given the following advice for
Call 3206276210:
Usually when this occurs, there may not be a /var/adm/sw/save/PHxx_yyyyy
directory so DO NOT try and swremove the patch.

Execute swmodify for each patch in this state to remove its reference
from the IPD.

swmodify -u PHxx_yyyyy.\* PHxx_yyyyy

Verify that the source depot does not contain any patches with
data_model_revision 2.10.
data_model_revision 2.10 is for 10.20 .

cd to source depot
find . -name INDEX -exec grep -l "data_model_revision 2.10" {} \; | more

If any are found, they will need to be swremoved from the source depot and a
good patch-source swcopied to the source depot.

Now swinstall the patches that were flagged by the check_patches.report,
insuring that the 'patch_match_target=true' option is used.

**************************

And yes I show the "data_model_revision 2.10"
as follows:

# [/software/PDC_FIRMWARE.43.22]# find . -name INDEX -exec grep -l "data_model_revision 2.10" {} \; | more
./catalog/dfiles/INDEX
./catalog/INDEX
./catalog/PHSS_28610/pfiles/INDEX
./catalog/PHSS_28610/KERN-RUN/INDEX
./catalog/BUNDLE/pfiles/INDEX
# [/software/PDC_FIRMWARE.43.22]# find . -name INDEX -exec grep -i "data_model_revision 2.10" {} \; | more
data_model_revision 2.10
data_model_revision 2.10
data_model_revision 2.10
data_model_revision 2.10
data_model_revision 2.10
data_model_revision 2.10
data_model_revision 2.10
data_model_revision 2.10

********************************

But I don't think I'm going to change anything.