Mismatched filesets after updating to version C.7.0 or later

Ignite-UX version C.7.0 fixes a defect in the pkg_rec_depot command. From Ignite-UX version C.6.0 to C.6.10, the command contained a defect that caused all the BOOT-KRN-11-XXfilesets to be included in every Ignite-UX-11-XXbundle in the recovery commands depot (/var/opt/ignite/depots/recovery_cmds).

Note:

This issue does not affect the network recovery bundle IUX-Recovery, any Ignite-UX-11-XXbundle from media, or the Web download version of Ignite-UX.

If you use the recovery commands depot to perform an update to Ignite-UX version C.7.0, it will end with warnings. If Ignite-UX is updated because you have started a make_tape_recovery command on a client from the Ignite server, the make_tape_recovery command will fail because of mismatched filesets.

You will only see this issue if you have installed the full Ignite-UX bundle B5725AA on the Ignite server, or if you have installed more than one Ignite-UX-11-XXbundle on the Ignite server.

To work around this issue, you have to perform one of the following:

1.Remove all Ignite-UX software from all clients that have installed Ignite-UX from a recovery commands depot containing Ignite-UX versions C.6.0 to C.6.10. Once the Ignite server has been updated to Ignite-UX version C.7.0 or later, Ignite-UX can be installed again from the recovery commands depot. Note that starting a make_tape_recovery command from the Ignite user interface will cause Ignite-UX to be installed from the recovery commands depot – you do not need to install Ignite-UX if you normally create recovery tapes this way.

2.After updating Ignite-UX to version C.7.0 or later and determining that you have mixed fileset revisions, perform the following tasks. First run the swlist command as follows to determine the revisions of the mixed filesets.

# swlist

grep

–i ignite

 

 

Ignite-UX-11-23

C.7.0.106

HP-UX

Installation Utilities for

Installing

11.23 Systems

 

 

Ignite-UX

 

C.6.1.44

HP-UX

System Installation Services

For each line in the output that shows Ignite-UX, perform the next action:

#swremove Ignite-UX,r=C.6.1.44

It is critical you provide the revision with the swremove command, or you might remove software you did not intend to remove. You must also use the revision shown in the swlist output, not the revision shown in the example swremove command. Normally, you should only see one line with the product Ignite-UX, however if you had mismatched filesets previously and never addressed the issue, it is possible you may see more than one line.

8