Are you installing a number of RPM's togther and this is one of them ?? if yes, are the other rpms installed successfully or not ?
if rpm -UIv is returning a non-zero code , it will by default treaed as failure.
Can you run this manually and check the retrun code ?
Also, how are you trying to install mutiple rpms ? , it is recommended to create a rpm group in the blpackage to do this.
I traced it back to one of the RPMs requiring a library newer than installed. Fix was to include the mysql-client library RPM that it required.
Even though the error above indicated that deploy job failed due to rpm already installed, it actually wasnt.
1 of 1 people found this helpful
If you need to install rpms, you should use a paj in install mode to install the rpm and its deps, this will avoid installing rpms that already exist. Rpm will fail out if you are trying to install/upgrade rpms that are already there so the problem is rpm here.
I second Bill's opinion.
So the challenge in doing it in PAJ is that not all RPMs are part of the Patch Catalog update. I'd have to stock it manually (which is an option, not the best one).
I've ran into this issue again in a BLpackage that installs MySQL and it's dependencies. One of the RPMs is perl-DBI. The BLPackage deploy job failed because perl-DBI was already installed by a developer.
Any suggestions on how to ensure that rpm -Uiv is handled correctly? I thought that if -Uiv option was used, it would ignore the condition when the installer finds that the RPM is already installed. I would expect that BL would handle this more gracefully.
Or is the only production-viable option (when you don't know what to expect as far as pre-installed RPMs on a target system) is via a PAJ?
Why are not all rpms in the catalog ?
-U does not handle installed packages. It fails. So maybe there is some other rpm option that handles installed packages.