Good morning

My customer is having an issue patching an OES 2 SP3 server from a ZCM server using the "zac up" command. Please see the below content:

Continue Yes/No [N]:y
Downloading xorg-x11-server-glx [100%] Done

Downloading xorg-x11-server-glx [100%] Done

Done [100%] Done


warning: waiting to reestablish exclusive database lock
dm_task_set_name: Device /dev/dm-21 not found
Command failed
24651 blocks
Stopping the service 'namcd'...done.
Starting the service 'namcd'... Done.
insserv: script ipmi.hp: service ipmidrv already provided!
Registry DB Check Ok
warning: waiting to reestablish exclusive database lock
warning: /etc/samba/smb.conf created as /etc/samba/smb.conf.rpmnew
warning: waiting to reestablish exclusive database lock
warning: waiting to reestablish exclusive database lock
insserv: script ipmi.hp: service ipmidrv already provided!
warning: waiting to reestablish exclusive database lock
warning: /etc/localtime created as /etc/localtime.rpmnew
insserv: script ipmi.hp: service ipmidrv already provided!
warning: waiting to reestablish exclusive database lock
insserv: script ipmi.hp: service ipmidrv already provided!
warning: waiting to reestablish exclusive database lock
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script ipmi.hp: service ipmidrv already provided!
warning: /usr/lib/jvm/java-1_5_0-ibm-1.5.0/jre/lib/security/java.security created as
/usr/lib/jvm/java-1_5_0-ibm-1.5.0/jre/lib/security/java.security.rpmnew
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script ipmi.hp: service ipmidrv already provided!
warning: waiting to reestablish exclusive database lock
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script ipmi.hp: service ipmidrv already provided!
There is no section with image '/boot/vmlinuz-2.6.16.60-0.54.5-smp'
Usage:
update-bootloader [operation] [options]

operation is one of --add, --remove or --refresh.

valid options are --help, --man, --image <file>, --initrd <file>,
--xen-kernel <file>, --xen, --default, --previous, --name <string>,
--force, --force-default.

There is no section with image '/boot/vmlinuz-2.6.16.60-0.69.1-smp'
Usage:
update-bootloader [operation] [options]

operation is one of --add, --remove or --refresh.

valid options are --help, --man, --image <file>, --initrd <file>,
--xen-kernel <file>, --xen, --default, --previous, --name <string>,
--force, --force-default.

There is no section with image '/boot/vmlinuz-2.6.16.60-0.77.1-smp'
Usage:
update-bootloader [operation] [options]

operation is one of --add, --remove or --refresh.

valid options are --help, --man, --image <file>, --initrd <file>,
--xen-kernel <file>, --xen, --default, --previous, --name <string>,
--force, --force-default.

There is no section with image '/boot/vmlinuz-2.6.16.60-0.85.1-smp'
Usage:
update-bootloader [operation] [options]

operation is one of --add, --remove or --refresh.

valid options are --help, --man, --image <file>, --initrd <file>,
--xen-kernel <file>, --xen, --default, --previous, --name <string>,
--force, --force-default.

There is no section with image '/boot/vmlinuz-2.6.16.60-0.93.1-smp'
Usage:
update-bootloader [operation] [options]

operation is one of --add, --remove or --refresh.

valid options are --help, --man, --image <file>, --initrd <file>,
--xen-kernel <file>, --xen, --default, --previous, --name <string>,
--force, --force-default.

There is no section with image '/boot/vmlinuz-2.6.16.60-0.99.1-smp'
Usage:
update-bootloader [operation] [options]

operation is one of --add, --remove or --refresh.

valid options are --help, --man, --image <file>, --initrd <file>,
--xen-kernel <file>, --xen, --default, --previous, --name <string>,
--force, --force-default.

warning: waiting to reestablish exclusive database lock
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script ipmi.hp: service ipmidrv already provided!
warning: waiting to reestablish exclusive database lock
insserv: script ipmi.hp: service ipmidrv already provided!
insserv: script ipmi.hp: service ipmidrv already provided!
Unable to complete RPM transaction: waiting to reestablish exclusive database lock

Error processing the ZAC command.
You have new mail in /var/mail/root

Customer reverted the system to an earlier version and tried the same patching procedure again, this time when the error message appeared instead of pointing to dm_task_set_name: Device /dev/dm-21 not found
Command failed

It was pointing instead to dm_task_set_name: Device /dev/dm-20 not found
Command failed

When examining the system, there does appear to be a path for /dev/dm20 yet unclear why it would be reporting this way, further it appears the system has been patched completely and that this may be a cosmetic error, but just needing to make sure that the process has completed or if it really did fail

Any thoughts ?