Bug 1160272 - typo in the path to the global configuration files
Summary: typo in the path to the global configuration files
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Pulp
Classification: Retired
Component: documentation
Version: 2.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 2.6.0
Assignee: Ina Panova
QA Contact: Irina Gulina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-04 13:38 UTC by Irina Gulina
Modified: 2015-02-28 22:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-28 22:43:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 606 0 None None None Never

Description Irina Gulina 2014-11-04 13:38:15 UTC
Document URL:

http://pulp-docker.readthedocs.org/en/latest/tech-reference/distributor.html


Describe the issue: 

Almost in the beginning, starting from: "The global configuration file for the docker_web_distributor plugin can be found in /etc/pulp/server/plugin.conf.d/docker_distributor.json."

it should be /etc/pulp/server/pluginS.conf.d/docker_distributor.json


missing S in plugins.

>> ls -l /etc/pulp/server/plugin.conf.d/
ls: cannot access /etc/pulp/server/plugin.conf.d/: No such file or directory

>> ls -l /etc/pulp/server/plugins.conf.d/
total 0

Comment 1 Irina Gulina 2014-11-04 13:45:54 UTC
This typo occurs twice on the give link. The second one is in the Export section:

The global configuration file for the docker_export_distributor plugin can be found in /etc/pulp/server/plugin.conf.d/docker_distributor_export.json

missing S in pluginS.conf.d

Comment 2 Ina Panova 2014-11-18 10:09:34 UTC
https://github.com/pulp/pulp_docker/pull/48

Comment 3 Randy Barlow 2014-12-12 18:55:32 UTC
Should this have a 2.6.0 target release?

Comment 4 Ina Panova 2015-01-06 09:04:05 UTC
fixed in pulp 2.6.0-0.2.beta

Comment 5 Brian Bouterse 2015-02-28 22:43:11 UTC
Moved to https://pulp.plan.io/issues/606


Note You need to log in before you can comment on or make changes to this bug.