Problems connecting to remote YUM package repositories
I'm trying to setup "Artifactory Pro Power Pack 3.9.0 (rev. 30199)" for Remote Repository connections to some YUM repo URLs that work fine with YUM directly but get "Connection failed: Error 404: Not Found" errors when testing with AF. None of the following baseurl's work, and these repo definitions are straight out of a working yum file:
Re: Problems connecting to remote YUM package repositories
Still blocked on this. Without resolution it's not looking like AF remote repos will be of much use to our organization. We've also tried a test instance of AF 4.x and it shows the same issue.
I've tried testing various levels of the https://packages.elastic.co/ directory hierarchy with AF's remote repo "test" button. The only one that AF accepts as legit is the top level URL itself. However, this is rejected by yum itself:
# repoquery --repofrompath=elktop,https://packages.elastic.co/ --repoid=elktop -q -a
failure: repodata/repomd.xml from elktop: [Errno 256] No more mirrors to try.
https://packages.elastic.co/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
and, when that AF remote repo is queried by yum, it too fails:
# repoquery --repofrompath=testelk,http://usr:pw@af-server:8081/artifactory/simple/elk-remote --repoid=testelk -q -a
failure: repodata/repomd.xml from testelk: [Errno 256] No more mirrors to try.
http://usr:pw@af-server:8081/artifactory/simple/elk-remote/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
For comparison, here's a very specific repo baseurl that works for yum but is rejected by AF's test button with a 404 error:
I went ahead and added the remote repo with the same URL as above anyway and tried it:
# repoquery --repofrompath=elkbeats,http://usr:pw@af-server:8081/artifactory/simple/elk-beats --repoid=elkbeats -q -a
failure: repodata/repomd.xml from elkbeats: [Errno 256] No more mirrors to try.
http://usr:pw@af-server:8081/artifactory/simple/elk-beats/repodata/repomd.xml: [Errno 14] HTTP Error 403 - Forbidden
I believe we've figured this out. It's a combination of two issues:
1) The S3 bucket(s) hosting the elastic.co repos apparently do not have the s3:ListBucket permission, which causes the AF "test" button to fail (with a 404 error) as well as attempts to browse to elastic.co repo paths in the browser.
2) Even though the AF "test" fails, the remote repo definition can still be saved. At that point, however, testing it showed a 403 error which I thought also came from S3. But, the 403 in fact came from AF as a result of the AF user not having deploy permissions on that remote repo. Once this permission was added, the remote repo pointing to one of elastic.co's repos began working!
Just recording the final outcome here for posterity...