The PAJ should be taking care of the deps.
where are you getting the dep error ? in what log ? can you get the logs from the /var/tmp/stage/ directory on the target showing the dep error.
also, I’m pretty sure that the dependency is the other way around w/ those particular rpms.
Are you trying to deploy individual rpms ?
Or are you using the Patch Anlayis Job results to deploy all missing ?
Yes I am trying to deploy individual rpms from the Patch Analysis job result. Is it possible any way to group the dependent rpms in Patch catalog or any other way ???
Hi Bill, I am getting error in Patch Deploy Job result, In commit stage.
That should be the main resaon of failure in dependency. Unfortunately I dont have a running Linux catalog to confirm this but you can check
When you package individual rpm does the blpackage created contain only that rpm(s) or more ? I do not think that this way it will fetch any dependencies automatically
Patching uses blyum (BLadelogic's private copy of yum on target), which during the deployment runs a compelete yum deploy.
What is the exact action you are using ? Right click on rpm and what action ?
1 of 1 people found this helpful
why are you trying the deploy individual rpms ? you should push all the missing rpms to the targets. if you want to push only a few rpms, you should change the filters on the paj to include only those rpms and then run analysis - that will include any dependencies.
Thanks Bill, Rohit
Actually my client want me to deployonly selected RPMs after the patch analysis. But the question was how to identify the dependencies of the RPMs before creating BLPackage.
As Bill said, I tested it by creating filter and it is working but still the concern is itrequire rerun of analysis to identify the dependency.
The existing system they have for the patch management is actually giving the list of missing patches and selecting one of missing patch gives the all dependant patches list which they can deployon target box. So they are expecting same functionality in BBSA. Partially we can achieve this as suggested by Bill.