Skip to main content

Trying to Elevate to Almalinux 8, but hitting a wall

Nikolay Nachev

I'm following this guide:

https://cpanel.github.io/elevate/

trying to upgrade CentOS 7.9 to Almalinux 8

but there is some permissions / repository issues I can't get around. Any idea why this is happening?

the elevate script tries to do that and comes with the same error:

when I try to 

sudo yum upgrade -y

I get the following error:

Loaded plugins: universal-hooks
https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
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 (CentOS 7 Extended Lifecycle Support by TuxCare),
 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=centos7-els ...

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

     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=centos7-els.skip_if_unavailable=true

failure: repodata/repomd.xml from centos7-els: [Errno 256] No more mirrors to try.
https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden

Comments

17 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  Just to rule out other Yum issues, does a plain "yum update" work on the machine?

    0
  • Nikolay Nachev

    No it did not.

    I narrowed the problem to having the wrong kernel version for some weird reason and I destroyed this server (which was a test server anyway) and cloned it again and this time I did not have this issue.

    Thanks for offering help though.

    Cheers!

    0
  • cPRex Jurassic Moderator

    You're very welcome!  If Yum itself wasn't working, there were likely deeper issues on the machine that needed to be dealt with before ELevate would work properly.

    0
  • Nikolay Nachev

    Unfortunately, I'm back here with the same problem and apparently it wasn't the wrong kernel version as I initially thought.

    I fully updated my production server (then yum was working no problem).

    Then I cloned it and ran it on another VPS, and when I ran yum on it - I get the same error as above:

    “/usr/bin/yum” reported error code “1” when it ended:  w/ /usr/bin/yum upgrade -y
Loaded plugins: universal-hooks
https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
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 (CentOS 7 Extended Lifecycle Support by TuxCare),
 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=centos7-els ...

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

     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=centos7-els.skip_if_unavailable=true

failure: repodata/repomd.xml from centos7-els: [Errno 256] No more mirrors to try.
https://repo.tuxcare.com/centos7-els/updates/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden

Often errors like this can be resolved by running `yum makecache`


    As I'm using an older version of WHM (as the newest one is not supported on CentOS 7.9), I have the following message in WHM:

    cPanel & WHM version 110 will be the last version that supports CentOS 7. The Extended Lifecycle Support program extends CentOS 7 support with cPanel & WHM version 110 to January 1, 2026. Read more about this program in the Extended Lifecycle Support OSes blog post. We encourage you to migrate to a supported operating system as soon as possible.

    Click the “Elevate to AlmaLinux 8” button below to read about a script you can use to upgrade cPanel & WHM installations on CentOS 7 to AlmaLinux 8.

    Only system administrators (root and root-level resellers) see this message.


    What I suspect is going on here - the new server, for some reason, isn't getting " The Extended Lifecycle Support " for some reason and its IP isn't getting passed so that it'll be able to update from the erroring out repo above.

    I have no idea how to get around fixing this or debugging this further though.

    Ideas?

    0
  • Nikolay Nachev

    Apparently I needed a license from TuxCare (that wasn't automatically issued by my hosting).

    0
  • Andrew
    Translate

    Glad you sorted this out, enjoy :)

    Andrew N. - cPanel Plesk VMWare Certified Professional
    Do you need immediate assistance? 20 minutes response time!* Open a ticket
    EmergencySupport - Professional Server Management and One-time Services

    0
  • Alexandros Androutsos

    Hello Nikolay Nachev,

    Could you please share how you got the license from TuxCare and how you applied it?

    0
  • Nikolay Nachev

    Sure.

    So basically you register here:

    https://portal.tuxcare.com/dashboard/products

    and purchase a license, you have to find where to do it in that dashboard, I don't remember the exact steps

    then to install the license on your machine, I believe I ran:

    sudo kc-ctl --register "your_license_key_here"

     
     
    0
  • Alexandros Androutsos

    Oh good. So what If I just want to upgrade to alma and don't care about the tuxcare license?
    I have 2 systems at the same state, one is older and doesn't have that issue but also does not use tuxcare, and one that was made later and has that issue.

    I don't believe I ever relied on tuxcare...

    0
  • Nikolay Nachev

    The license was pretty cheap (like $6 for a month I think).

    I got it because there was no way I could upgrade without it (the elevate test script was producing errors that required a tuxcare license to get fixed).

    0
  • cPRex Jurassic Moderator

    In general, if you are running cPanel on a CentOS 7 machine, you should be getting that Tuxcare service applied to your machine by us, without you having to do anything else on the server.

    If that isn't happening, could you create a ticket?

    0
  • Explicit

    I have same issue, so in order to do upgrade, we need to buy licence from tuxcare ?

    0
  • cPRex Jurassic Moderator

    Explicit - you should not need to purchase anything to perform that upgrade.  If that isn't working how you expect please create a ticket so this can be investigated on your machine.

    0
  • Explicit

    The thing is that i buy license for that server over hetzner, they don't do support, and i cannot open ticket oc cpanel with their server IP - what is the best way to open ticket ?

    0
  • cPRex Jurassic Moderator

    Your provider should be offering support for the licenses they sell.  If that isn't happening, can you please email cs@cpanel.net to let us know about that situation?

    0
  • Explicit

    Thx!

    0
  • cPRex Jurassic Moderator

    You're very welcome!

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post