GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

RHEL / Centos 7 compatibility - yum repository

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • RHEL / Centos 7 compatibility - yum repository

    Hello,

    is there any ETA when RHEL / Centos 7 *yum Repository* is ready? Or when there are the needed Binaries?
    Right now it fails with: "http://repo.percona.com/centos/7/os/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found"

    Thank you
    Andreas Schnederle-Wagner

  • #2
    really noone?

    Comment


    • #3
      Hi Andreas, I checked with an expert on the Percona XtraBackup team on this, he said it sounds like you are trying to use the production repo which is currently still unavailable (only centos7 testing repo is available).

      Here's a tentative plan for centos7 releases:
      Aug 29 - PS 5.5 and 5.6
      Sept 5 - PXC 5.5 and 5.6
      Sept 12 - PXB 2.2 and PT

      Sorry about your trouble and I hope this helps.
      Tom
      Is this an emergency? Get immediate assistance from Percona Support 24/7. Click here.

      Comment


      • #4
        Any updates on centos7 releases PS 5.5 and 5.6 ?

        Comment


        • #5
          Here's the latest... http://repo.percona.com/centos/
          Is this an emergency? Get immediate assistance from Percona Support 24/7. Click here.

          Comment


          • #6
            Any update on this? The Centos 7 repository is still empty (apart from xtrabackup).

            Is it safe to use the testing repo and switch to the production repo later?

            Comment


            • #7
              Any idea about the status/ETA of the Percona Server RPM's for CentOS 7.

              Comment


              • #8
                There's a related thread here: Summary (might help here): the root cause is AMI image (and Amazon) itself. it doesn't use redhat version numbering like 5,6,7. it uses dates for releases like 2014.09. it doesn't use official Centos and RedHat repositories and uses internal amazon repositories with different structure and logic.
                failure from above is caused by "latest" symlink in URL which points to latest Amazon release. we can't set such symlink pointed exclusively to Percona Centos 6 repository.

                I see 2 options there to fix that:

                * do not allow AMI to define $releasever as "latest" and set it manually in percona-release.repo. you need to replace $releasever with exact Centos version in percona-release.repo. example command to replace on Centos 6 based AMIs: sed -i 's/$releasever/6/g' /etc/yum.repos.d/percona-release.repo.
                * do not use Amazon AMIs in such case, because they are not exactly the same OS, it's some kind of OS fork made by Amazon and adjusted exclusively for Amazon services, software and infrastructure. use Centos AMIs.

                Original thread here: http://www.percona.com/forums/questi...s-to-be-broken
                Is this an emergency? Get immediate assistance from Percona Support 24/7. Click here.

                Comment

                Working...
                X