Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amazon Linux support #74

Open
mcrauwel opened this issue Sep 16, 2018 · 0 comments
Open

Amazon Linux support #74

mcrauwel opened this issue Sep 16, 2018 · 0 comments

Comments

@mcrauwel
Copy link
Member

mcrauwel commented Sep 16, 2018

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 4.10.12
  • Ruby: 1.8.7
  • Distribution: Amazon Linux AMI release 2018.03
  • Module version: 2.0.0

How to reproduce (e.g Puppet code you use)

 class { '::proxysql':
    listen_port              => 3306,
   }

What are you seeing

Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install proxysql' returned 1: One of the configured repositories failed (ProxySQL YUM repository),
 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. Disable the repository, 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 proxysql_repo

     4. 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=proxysql_repo.skip_if_unavailable=true

failure: repodata/repomd.xml from proxysql_repo: [Errno 256] No more mirrors to try.
http://repo.proxysql.com/ProxySQL/proxysql-1.4.x/centos/latest/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

However with this change:

  class { '::proxysql':
    listen_port              => 3306,
    manage_repo		     => false,
  }

The module works as expected.

Created upstream issue sysown/proxysql#1694 to request releasever = latest after that would be approved the default module can claim Amazon Linux 2018.03 support

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant