the redhat patch levels are pretty arbitrary – do they really mean anything?
we did not have "product enhancement advisory" checked
Has anyone used the "By Update Level" option?
I've done that and chose the default op "1" in the field that appears. But when updating the catalog I get:
Error 29-dec-2011 16:07:29 Fatal error while updating metadata : 1
Some folders are created in my repository:
But no files. I'm not sure about the update level I've selected and the documentation only speeks of "select your desired update level".
[29 Dec 2011 16:07:28,669] [PSU-Thread-1] [INFO] [u94434:PT3_BLAdmins:] [Patch-Metadata-Updator] ntlm authentication scheme selected
[29 Dec 2011 16:07:28,904] [PSU-Thread-1] [INFO] [u94434:PT3_BLAdmins:] [Patch-Metadata-Updator] Response content length is not known
[29 Dec 2011 16:07:29,232] [PSU-Thread-1] [INFO] [u94434:PT3_BLAdmins:] [Patch-Metadata-Updator] ntlm authentication scheme selected
[29 Dec 2011 16:07:29,263] [PSU-Thread-1] [INFO] [u94434:PT3_BLAdmins:] [Patch-Metadata-Updator] Response content length is not known
[29 Dec 2011 16:07:29,498] [PSU-Thread-1] [FATAL] [u94434:PT3_BLAdmins:] [Patch-Metadata-Updator] Fatal error while updating metadata
at com.bmc.sa.patchfeed.redhat.util.RhnWebService.getISODownloadUrls(Unknown Source)
at com.bmc.sa.patchfeed.redhat.RedHatMetadataManager.processOnlineUpdateLevelSKUs(Unknown Source)
at com.bmc.sa.patchfeed.redhat.RedHatMetadataManager.processOnlineSKUs(Unknown Source)
at com.bmc.sa.patchfeed.redhat.RedHatMetadataManager.getFeedMappings(Unknown Source)
at com.bmc.sa.patchfeed.redhat.RedHatFeedUpdator.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
[29 Dec 2011 16:07:29,498] [WorkItem-Thread-1] [ERROR] [u94434:PT3_BLAdmins:] [Patch-Metadata-Updator] Fatal error while updating metadata : 1
What seems like a failure to authenticate to the proxy, but windows patch downloading works.
What is the Filter details ?
Provide your exact filter options ? Channel ? OS and Architecture ?
Are you aware of a Patch Update Level released for this ?
Is the new ‘redhat-release’ rpm included in the rpms being deployed ?
Below you seem to have some problems downloading the files.
In fact nothingt is being deployed. It is indeed as you state: The downloading fails
Does any other filter option work in your environment, I mean a filter different than update level ?
I am asking this to rule out any problems with the environment when it comes to downloading stuff for the catalog update.
From the very first look, it looks like a BUG, as no matter what is wrong, it should not throw you a java exception
There are two update levels for this version of Redhat as far as I know, 6.1 and 6.2
Try running with some other filter type.
That was a good idea. Choosing the default filter type gives me a more descriptive error:
Error 30-dec-2011 12:27:56 Error while updating feed: Either service is Unavailable or credentials are Invalid. Failed to connect to RHN xml rpc server.
I'll check with my colleagues if the credentials are correct. I'll keep you guys posted.
You can verify the credentials by using them to try to access https://rhn.redhat.com/
Also, check any Proxy Server configuration is correct (re-do the configuration to be sure)
This is in Console Menu option Configuration => Patch Global Configuration
Credentials were indeed wrong.
After changing them I've tried the level option again but still sthe same error.
The default filter works tough.
I'll create an issue to make sure it gets fixed
Where did you change the credentials? You must set them in the catalog.
Yes, I've changed them in the catalog. But it really seems to have something to do with the "By Update Level" filter since the other filter types work.