I managed to make it work, thanks to @bmbouter from the irc pulp channel
for pointing to the right link
(https://pulp-rpm.readthedocs.org/en/latest/user-guide/recipes.html#mirror-a-remote-repository)
There is some inconsistency in URL generation from my point of view, or
at least is not standardized. For troubleshooting purposes I created the
foreman repo as per the link exercise and managed to access to:
https://localhost/pulp/repos/foreman/
the other repos became "available" but in different location:
https://localhost/pulp/repos/repos/pulp/pulp/demo_repos/zoo/
and the key modifier was:
--relative-url=
At the creation repo moment, if you specify "--relative-url=" then Pulp
works perfect, but if don't it takes the trailing URL from:
--feed=
which, I think, should not happen.
Related to this, I think that ideally the definitive URL should be shown
when:
pulp-admin rpm repo list
or another command.
To know the proper URL was by:
$ pulp-admin rpm repo list --repo-id=zoo*--details*
+----------------------------------------------------------------------+
RPM Repositories
+----------------------------------------------------------------------+
Id: zoo
Display Name: None
Description: None
Content Unit Counts:
Erratum: 4
Package Category: 1
Package Group: 2
Rpm: 32
Notes:
Scratchpad:
Checksum Type: sha256
Importers:
Config:
Feed:https://repos.fedorapeople.org/repos/pulp/pulp/demo_repos/zoo/
Id: yum_importer
Importer Type Id: yum_importer
Last Sync: 2016-03-26T16:55:35Z
Repo Id: zoo
Scratchpad:
Previous Skip List:
Repomd Revision: 1331832478
Distributors:
Auto Publish: True
Config:
Checksum Type: sha256
Http: True
Https: True
***Relative URL: repos/pulp/pulp/demo_repos/zoo/*
Distributor Type Id: yum_distributor
Id: yum_distributor
Last Publish: 2016-03-26T17:05:47Z
Repo Id: zoo
Scratchpad:
Auto Publish: False
Config:
Http: True
Https: True
*Relative URL: repos/pulp/pulp/demo_repos/zoo/*
Distributor Type Id: export_distributor
Id: export_distributor
Last Publish: None
Repo Id: zoo
Scratchpad:
Probably I am not the only one facing this issue, then I think it could
be better documented in troubleshooting section of docs, filing feature
request :D
Thanks!
On 03/27/2016 06:11 AM, Michael Hrivnak wrote:
Make sure you have a trailing slash. I get these differing results:
$ curl -k -I https://localhost/pulp/repos/
HTTP/1.1 200 OK
$ curl -k -I https://localhost/pulp/repos
HTTP/1.1 404 Not Found
Michael
On Sat, Mar 26, 2016 at 3:06 PM, Kodiak Firesmith
<[email protected] <mailto:[email protected]>> wrote:
Start with all of the *_log files in /var/log/httpd/. There will
be clues, and possibly some access denied messages.
On Mar 26, 2016 2:57 PM, "Alejandro Cortina"
<[email protected]
<mailto:[email protected]>> wrote:
Hi everyone,
I am new to pulp and longtime sysadmin. I am using the
official install documentation for the server and everything
goes fine for CentOS7. I can create repos and sync them, but
when trying to browse them I get:
Not Found
The requested URL /pulp/repos was not found on this server.
Since I will use ansible I don't need to use pulp-consumer,
but I cannot find any documentation related to clients without
pulp-consumer setup.
Please, help!
Can someone please point me in the right direction?
Thank you!
Alex
_______________________________________________
Pulp-list mailing list
[email protected] <mailto:[email protected]>
https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________
Pulp-list mailing list
[email protected] <mailto:[email protected]>
https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list
