Actions
Issue #2038
closedThe nectar config pulp_streamer gets doesn't seem to include plugin-level settings
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
Platform Release:
2.8.7
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 5
Quarter:
Description
pulp_streamer gets its nectar config (which ultimately is mapped to a requests config) from the platform. However, the platform does not appear to load the plugin-level configuration from /etc/pulp/server/plugins.conf.d/ and thus any configuration applied there won't get used when performing requests.
All of the above is pure conjecture based on the downstream bug and my chat with the reporter in freenode.
A good way to confirm this would be to:
1. Set up a proxy and make sure traffic goes through that proxy
2. Configure Pulp to use the proxy in the plugin configuration
3. Perform an on-demand sync
4. Try to download an RPM
Actions
The pulp_streamer now uses the plugin-wide proxy config
An importer has a configuration file in /etc/pulp/server/plugins.conf.d/ that can, among other things, configure the proxy used for the plugin. Previously, the streamer was only using the importer configuration that is present on the
Importer
module.Although the most sensible thing to do is have the importer configuration available on the Importer model object, this would require a great deal of cleanup since importer/distributor models and configuration are a mess of old and new, with the configuration spread all over the place. This should be cleaned up as part plugin API work we do for Pulp.
closes #2038