Thanks for the reply, i want to know , do i have to load the required RPMs in the depot via Depot -> New -> Software -> RPM ?
Once i add the required rpms then i created BLPackge and its RPM Group and after that i created one Deploy Job for Installation of BLPackage and getting the error messages again and again that some other rpms are missing and adding one by one
Could you please let me know how to resolve the missing rpms issue? Do i have to check the log every time for missing rpms? Or any other way to resolve the missing RPMs issue while running the RPM Deploy Job?
Let say for example for installing / upgrading httpd service in Linux it requires 10-14 rpms , but if i do not know which are those , then do i have to check the log only for installing / upgrading?
Thanks for your help
When you create an RPM group , the underlying command issues becomes
rpm -uiv <list of all rpms in the rpm group>
This lets the rpm command to automatically sequence dependencies for installation, But yes this needs all required dependencies to be in the list.
If you dont know all the dependencies at the time of package creation, than it is a problem
There are ways to do this:-
- pre-fetch the information about rpm, use the rpm command line query options to get the list of dependencies and package all those.
- What I will do personally is to make my life easy
- If its not a custom rpm, The best one and easiest one is to use something like YUM. For this you need to have your yum repository populated for a particualar Redhat/Suse distribution. This makes sure that the rpm you are trying to install is present in the repostory with all its dependencies.
- This is supported by the Patch functionality of BladeLogic, I will use patch Analysis and put one rpm in the include list and will go for install mode, the analysis result will show the rpm as missing and will return other dependencies automatically, I will use the patch deploy job. Remember the install mode.
I am not sure if many of the gurus will agree with me or not
When using an rpm group, the RPM order does not matter as the rpm command sorts it all out. And the easiest way is to use YUM. Export your redhat patch repository via nfs and setup a yum repo to point to that nfs mount on your target server (Google it, if you don’t know how to do those two steps), then just install packages via YUM. YUM will autoresolve dependencies.
The easiest way to do this in BBSA is to create a patch catalog. Then create Patching Job, on the 2nd or 3rd tab of the wizard you set the job to 'install mode' instead of update mode. then you specify the package you want to install in the 'includes'. run the paj, this will tell you what dependencies need to be installed. when you run remediation all of the property deps will be pushed to the target.
the benefit of this is that you can push out httpd to a bunch of hosts, and if they all require different dependencies, the Patching Job will work that out.