Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3602

MaxScale 2.4.11 and older can no longer be installed using mariadb_repo_setup

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.4.9, 2.4.10, 2.4.11, 2.5.2, 2.3
    • Fix Version/s: N/A
    • Component/s: Repositories
    • Labels:
      None
    • Environment:
      CentOS/7

      Description

      The URLs created by the mariadb_repo_setup tool do no longer work for versions 2.4.11 or older, e.g. when trying to set up a system on CentOS 7 using

      mariadb_repo_setup --mariadb-maxscale-version=2.4.11
      

      the setup script runs just fine, but trying to actually install maxscale with

      yum install maxscale
      

      then fails with:

      [root@localhost ~]# yum install maxscale
      Loaded plugins: fastestmirror
      Loading mirror speeds from cached hostfile
       * base: ftp.plusline.net
       * extras: ftp.plusline.net
       * updates: ftp.plusline.net
      mariadb-main                                                                                                   | 3.4 kB  00:00:00     
      https://dlm.mariadb.com/repo/maxscale/2.4.11/yum/rhel/7/x86_64/repodata/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 (MariaDB MaxScale),
       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=mariadb-maxscale ...
       
           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 mariadb-maxscale
              or
                  subscription-manager repos --disable=mariadb-maxscale
       
           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=mariadb-maxscale.skip_if_unavailable=true
       
      failure: repodata/repomd.xml from mariadb-maxscale: [Errno 256] No more mirrors to try.
      https://dlm.mariadb.com/repo/maxscale/2.4.11/yum/rhel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
      

        Attachments

          Activity

            People

            Assignee:
            dbart Daniel Bartholomew
            Reporter:
            hholzgra Hartmut Holzgraefe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration