Why would you want to uninstall patches? won’t newer patches replace them?
I assume you are on 8.x. The Solaris patch catalog update should be run, every time it updates, it marks the patches as obsolete according to the latest metadata. Any patch with IS_OBSELETE=true are the ones which have been marked as obsoleted.
Running a solaris patch analysis with such an updated catalog should tell you the missing patches, which when installed will automatically take care of the obsoleted ones. This way makes it sure that you don’t break any dependencies.
The uninstall is not a part of the BladeLogic patching process. Even if you manage to automate it through BladeLogic, its not a good ideas as you will struggle to satisfy the dependencies many a times.
Solaris admin team wanted to check the obsoleted patches & uninstall them without doing any patching job. They wanted to confirm, is it possible using bladelogic?
Thanks for your update. Your update helps me alot.
I've executed patch analysis job on solaris box. In the log it gave me as below:
Patch '118666-30' is marked as obsolete.It will be skipped from analysis results.
But actually the patch '118666-30' is not existed on the target server. The same we can check using the below command:
showrev -p |grep 118666-30
According your update, where this patch existed? existed on target server or patch repository?
If it's on patch repository, how can we identify which patch is obsoleted, which is currently lying on the target server.
Why? This seems like a good way to break your system.
Also, won’t the obsoleted patches be replaced by the current patch once it’s applied?
Can we get the list of obsoleted patches on solaris server. Because my patch analysis job logs says... so and so patch has been asboleted and skipping from analysis. But that skipped patch is not lying on the target server. That patch is lying only in patch repository.
1. When patch is absoleted, it should be automatically deleted from patch repository, where as that patch is still existing in my patch repository. Unnecessarily my file server size increasing.
If i'm wrong, plesae suggest me the correct way.
There is currently no cleanup mechanism for the file system. You can submit an rfe for that.
You can remove the irrelevant patches, either via the blcli or via the gui. Once they are flagged as irrelevant they are not used during the deploy.
I still do not understand why your admins want to uninstall obsolete patches – why do they want to do that?
Because they are expecting wonders from Bladelogic .
could you clarify this please:
1. My patch analysis says "Patch '118666-30' is marked as obsolete.It will be skipped from analysis results." means, is bladelogic talking about the patch (118666-30) which is lying in patch repository or on target server.
2. If it's talking about patch repository then how can I identify which patches are obsoleted on target server.
Please help me out.
By Obsolete, it means obsolete by the Solaris vendor. This implies that this patch is no longer relevant, rather a new patch has been issued with a new patch id which replaces this patch.
If patch 118666-30 has been marked as obsolete, it will have a ‘Obsolete by’ patch which is meant to replace this.
The Patch Catalog is the representation of your patch repository in these terms. The actual payload ( the file) of the patch id.zip lying on the physical file system on the file server doesn’t have any role here.
A obsolete patch will never be shown as missing on a target server, the new patch which replaces it can be in the missing list if applicable.
As Bill, pointed out currently there is no way of cleaning up the FS to get rid of this physical payload.
Hope this makes sense to you.
If you live browse the target server and look at the patches object you will see all the patches currently installed on the system. But we do not show if they are now flagged as obsolete or not.
The very process of patch analysis determines if any patches on the target are obsolete and will show the replacement patch. There is no need to uninstall obsolete patches, infact it’s probably dangerous to do so.
I think the customer is confused here by what they see in the catalog vs what is on the target.
Thanks a lot,
one final question:
Consider, I executed the patching job, the job completed successfully and job identified the obsoleted patches and removed those patches by installing their superseded patches.
Now, I wanted to rollback (undo) the patching job, in this situation, how bladelogic can reinstall the removed obsoleted patches.
Does bladelogic take backup before doing patching?
Thanks a lot. Thanks for your valuable inputs.