New Contributor

The yum doesn't have enough cached data in Clearpass

Hi all,


I'm trying to update Clearpass in CLI, which is 6.7.9 now and it should be updated to 6.7.10 or 6.7.11.

But there is some issue has occured as below logs.


I couldn't proceed update from this point, and I also have tried to patch-rollback and factory-reset as well but nothing has changed.


Does anyone experienced this kind of issue?


How can I reach the mode that "yum" command can be run?






Installing patch from=CPPM-x86_64-20190107-clearpass-6.7-updates-10-aruba-67-patch.signed.tar
Extracting patch...
INFO - CPPM-x86_64-20190107-clearpass-6.7-updates-10-aruba-67-patch.signed.tar is signed
INFO: Preparing ...
INFO: Running pre-install scripts ...
INFO: Cleaning up unused kernels...
INFO: - Stopping Policy Manager services...
INFO: - Policy Manager services are stopped.
INFO: Stopping ClearPass Async Netd and Clearpass System Monitor Service...
INFO: Applying patch ...
INFO: This will take a few minutes to complete. Please wait ...
ERROR: Error updating yum cache:
Loaded plugins: fastestmirror
Cleaning repos: 20180614-clearpass-6.7-updates-5
: 20181003-clearpass-6.7-updates-7
: 20190107-clearpass-6.7-updates-10 20190214-cluster-join-hotfix
: 20190423-clearpass-6.7-updates-11 6.7.0_source-rollback-package
Cleaning up everything
Loaded plugins: fastestmirror
file:///var/avenda/platform/patches/20190423-clearpass-6.7-updates-11/rpms/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/avenda/platform/patches/20190423-clearpass-6.7-updates-11/rpms/repodata/repomd.xml"
Trying other mirror.

One of the configured repositories failed (20190423-clearpass-6.7-updates-11),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:


1. Contact the upstream for the repository and get them to fix the problem.


2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).


3. Run the command with the repository temporarily disabled
yum --disablerepo=20190423-clearpass-6.7-updates-11 ...


4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable 20190423-clearpass-6.7-updates-11
subscription-manager repos --disable=20190423-clearpass-6.7-updates-11


5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice


yum-config-manager --save --setopt=20190423-clearpass-6.7-updates-11.skip_if_unavailable=true


failure: repodata/repomd.xml from 20190423-clearpass-6.7-updates-11: [Errno 256] No more mirrors to try.
file:///var/avenda/platform/patches/20190423-clearpass-6.7-updates-11/rpms/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/avenda/platform/patches/20190423-clearpass-6.7-updates-11/rpms/repodata/repomd.xml"
ERROR: Applying patch failed: Package upgrade failed
Time taken to install this patch is 3 minute(s) and 37 second(s).
Exiting with 255



MVP Guru

Re: The yum doesn't have enough cached data in Clearpass

Please work with Aruba TAC. I have not seen this before, and you probably need TAC to get it resolved.

If you have urgent issues, please contact your Aruba partner or Aruba TAC (click for contact details).
Search Airheads
Showing results for 
Search instead for 
Did you mean: