Build Docker images fails with - RabbitMQ install failure - HTTPS Error 403 - Forbidden

[saintdle]

For the image: Building and pushing weathervane-rabbitmq image.

Step 10/11 : RUN chmod +x /entrypoint.sh &&     chmod +x /usr/local/bin/rabbitmqadmin &&    chmod 600 /var/lib/rabbitmq/.erlang.cookie &&     rpm --import https://github.com/rabbitmq/signing-keys/releases/download/2.0/rabbitmq-release-signing-key.asc &&   yum install -y erlang &&     yum install -y https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.7.17/rabbitmq-server-3.7.17-1.el7.noarch.rpm &&    rabbitmq-plugins enable rabbitmq_management &&      yum -y clean all
 ---> Running in d86a987981f1
Loaded plugins: fastestmirror, ovl
Determining fastest mirrors
 * base: d36uatko69830t.cloudfront.net
 * epel: mirror.freethought-internet.co.uk
 * extras: d36uatko69830t.cloudfront.net
 * updates: d36uatko69830t.cloudfront.net
https://dl.bintray.com/rabbitmq-erlang/rpm/erlang/21/el/7/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 (rabbitmq-erlang),
 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=rabbitmq-erlang ...

     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 rabbitmq-erlang
        or
            subscription-manager repos --disable=rabbitmq-erlang

     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=rabbitmq-erlang.skip_if_unavailable=true

failure: repodata/repomd.xml from rabbitmq-erlang: [Errno 256] No more mirrors to try.
https://dl.bintray.com/rabbitmq-erlang/rpm/erlang/21/el/7/repodata/repomd.xml: [Errno 14] HTTPS Error 403 - Forbidden
The command '/bin/sh -c chmod +x /entrypoint.sh &&  chmod +x /usr/local/bin/rabbitmqadmin &&    chmod 600 /var/lib/rabbitmq/.erlang.cookie &&     rpm --import https://github.com/rabbitmq/signing-keys/releases/download/2.0/rabbitmq-release-signing-key.asc &&   yum install -y erlang &&     yum install -y https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.7.17/rabbitmq-server-3.7.17-1.el7.noarch.rpm &&    rabbitmq-plugins enable rabbitmq_management &&      yum -y clean all' returned a non-zero code: 1

[hrosenbe]

Thank you for filing this issue. We had not rebuilt this image in the last few weeks and had not run into this problem. I did a build on a clean system and see the same error that you are reporting. We need to test your fix, and make sure that the version of Erlang you used is fully compatible (and performance neutral) with RabbitMQ. We probably won't be ready to merge the pull request until sometime next week.