There have been some reported problems specifically w/ patch clusters. I have been using solaris patching successfully w/ SP7P4, but I am using OS filters, not the cluster filters.
I believe the downloader is using the ‘Oakland’ user agent (java) to do the download, so you may need to check that that is allowed outbound, though that should not have changed.
Was this working pre-sp7p4 w/ the old sunsolve site and is now failing?
Thank you Bill.
We have it working using the OS filters, we just can't get it to work using cluster filters.
We are on sp7p4 and everything is working fine other than the cluster filtering.
Open a ticket w/ support
That will be my next step. We have a ticket open with Oracle to make sure that the Cluster name's are what they should be.
Once we have concluded its not a problem with Oracle I will open a ticket with BMC.
Thank you again.
On a related note, has anyone else seen problems downloading some patches on the patch catalogue update since the Oracle changes? We are seeing some HTTP 403 errors when doing the catalog update for specific patches.
If we connect directly to the Oracle pages with the support account, it does not see the patches either, so it looks like the support accounts may be restricted on the patches that they can download. This then really slows down the downloads though as it seems to wait nearly 3 minutes between patches if it gets a 403 error.
1 of 1 people found this helpful
The issue Paul mentions appears to be that our support contract does not allow access to all Oracle Solaris patches - there are a subset of 89 patches to which our contract doesn't allow downloads.
When BladeLogic comes to download these it appears to pause for around 3 minutes even though Oracle reply with a 403 status code.
What I'd like to see if BladeLogic understanding that 403 is a valid code and moving on immediately rather than spending nearly 5 hours rattling, slowly, through a small number of patches it'll never get
We received the same issues that everyone else is having.
We really need to be able to filter by cluster so if anyone gets that working please let us know.
In regards to my original issue with using cluster filters we have determined the solution.
We determined that the issue is with Oracle's cluster naming. When we use the old cluster name (provided by Solaris and used in BBSA Console) it works fine.
To clarify, the new cluster names from Oracle's support site are not the ones that need to be used by the downloader cluster filter.
The cluster name we used is just:
Recommended OS Cluster Solaris 10 SPARC
For the 89 patches you cannot get access to - I believe you should work w/ oracle to resolve the entitlement issue. those patches might have/be dependencies w/ patches you do have access to and cause those not to deploy properly.
Do you get a %age of Oracle sales then Bill?
The full error when attmpting to download the patch using the same credentials as specified in the BL settings is:
"You do not have the following permissions to download Patch 142297-01 (Vintage Solaris). Please contact Oracle Support Sales to extend your support contract to include access to this patch."
We'll do some more digging to see if we have any further support contracts but I don't see "Purchase more support" being a great answer if it's BladeLogic automatically attempting to download everything Sun/Oracle ever released.
Short term, you could create a smart group of patches that you want to exclude from analysis (the ones you don’t have access to), and add that group to an exclude list in the PAJ.
My main issue, as the administrator of the core of our implementation, is that the catalog update job takes 6hours or more each time it's run.
I'm pretty sure we don't have any of the products we're not downloading patches for so analysis jobs shouldn't be a problem.
But each week I have to review the success of the catalog updates and manually review the results of 89 patches I know we're not able to download.
When you run the catalog update job do you have the option to download patches checked?
Yes - we've experienced this problem since the very first update which successfully downloaded a good few Gb of content.
The next build probably needs to do a search and replace on Sunsolve btw