Unable to install pbis on Graviton2 centos 7 instance

[nancy.akwen]

[root@ip-10-237-100-132 yum.repos.d]# yum clean all; yum makecache
Loaded plugins: fastestmirror
Cleaning repos: base epel extras pbise updates
Loaded plugins: fastestmirror
Determining fastest mirrors
epel/aarch64/metalink | 19 kB 00:00:00
* base: download.cf.centos.org
* epel: d2lzkl7pfhq30w.cloudfront.net
* extras: download.cf.centos.org
* updates: download.cf.centos.org
base | 3.6 kB 00:00:00
http://mirror.es.its.nyu.edu/epel/7/aar ... repomd.xml: [Errno 12] Timeout on http://mirror.es.its.nyu.edu/epel/7/aar ... repomd.xml: (28, 'Connection timed out after 30001 milliseconds')
Trying other mirror.
epel | 5.4 kB 00:00:00
extras | 2.9 kB 00:00:00
https://repo.pbis.beyondtrust.com/yum/p ... repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.



One of the configured repositories failed (PBISE- local packages for aarch64),
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=pbise ...

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 pbise
or
subscription-manager repos --disable=pbise

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
compromise:

yum-config-manager --save --setopt=pbise.skip_if_unavailable=true

failure: repodata/repomd.xml from pbise: [Errno 256] No more mirrors to try.
https://repo.pbis.beyondtrust.com/yum/p ... repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
[root@ip-10-237-100-132 yum.repos.d]#


ProComputers CentOS-7.9-arm64-Minimal-8GiB-HVM-20210702_145438-3e660cbc-86ec-49f5-9acb-5e16047e127a

[TrevorH]

This 'pbis' thing appears to be a pay-for, subscription repo and not something we can advise on here.