Actions
Bug #29449
closedMinor fixes for developing for pulp3
Difficulty:
Triaged:
Yes
Description
Not sure if this is a feature or a bug.
I recently tried to connect my Katello forklift to an external pulp-server in order to test/develop against the latest pulp3 and pulp_deb for pulp3.
After manually replacing the settings for pulpcore in the smart_proxy_features
-table, I had the problem that repository could not be created because of a 404.
Turns out Katello tried to get /pulp/api/v3//status/
on the pulp3-server, which does not work. It has to be /pulp/api/v3/status/
.
After that worked, katello was not able to authenticate because the Config sent to the API-connector did not include username and password.
So I added the possibility to configure them in the above mentioned settings, where the pulp_url
is also defined.
Actions