I'm getting Error while doing Yum update because of this I'm unable to update the cPanel to latest stable version
yum update
Loaded plugins: fastestmirror, rhnplugin, universal-hooks
This system is receiving updates from CLN.
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 24 kB 00:00:00
* EA4: 185.15.22.168
* cpanel-addons-production-feed: 185.15.22.168
* cpanel-plugins: 185.15.22.168
* epel: mirrors.coreix.net
http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
It looks like you encountered an issue when performing the operation.
Please check if the issue related to CloudLinux repositories.
Usually our repositories contain "cloudlinux" word in their name.
If it does, check our knowledgebase for a possible solution or contact support:
www.cloudlinux.com
In other cases, please contact your system administrator to fix the issue.
One of the configured repositories failed (MariaDB102),
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=MariaDB102 ...
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 MariaDB102
or
subscription-manager repos --disable=MariaDB102
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=MariaDB102.skip_if_unavailable=true
failure: repodata/repomd.xml from MariaDB102: [Errno 256] No more mirrors to try.
http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
yum update
Loaded plugins: fastestmirror, rhnplugin, universal-hooks
This system is receiving updates from CLN.
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 24 kB 00:00:00
* EA4: 185.15.22.168
* cpanel-addons-production-feed: 185.15.22.168
* cpanel-plugins: 185.15.22.168
* epel: mirrors.coreix.net
http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
It looks like you encountered an issue when performing the operation.
Please check if the issue related to CloudLinux repositories.
Usually our repositories contain "cloudlinux" word in their name.
If it does, check our knowledgebase for a possible solution or contact support:
Support Portal - CloudLinux

In other cases, please contact your system administrator to fix the issue.
One of the configured repositories failed (MariaDB102),
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=MariaDB102 ...
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 MariaDB102
or
subscription-manager repos --disable=MariaDB102
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=MariaDB102.skip_if_unavailable=true
failure: repodata/repomd.xml from MariaDB102: [Errno 256] No more mirrors to try.
http://yum.mariadb.org/10.2/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found