Bug 1388629

Summary:	Pulp stores puppet publish location with repository
Product:	Red Hat Satellite	Reporter:	Stephen Benjamin <stbenjam>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.3.0	CC:	bbuckingham, cwelton
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-02 20:59:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Stephen Benjamin 2016-10-25 19:13:05 UTC

Description of problem:

When you change the path of puppet_content_dir in /etc/foreman-proxy/settings.d/pulp.yml and republish a content view, it does not take effect as it appears Pulp stores the publish location with the repository and does not read it again.


Version-Release number of selected component (if applicable):
6.3 nightly

How reproducible:
Always

Steps to Reproduce:
1. Create a content view on Puppet 3 that publishes to /etc/puppet/environments
2. Upgrade to Puppet 4
3. Republish content view

Actual results:
Content view is still published to /etc/puppet/environments

Expected results:
Content view goes to new location, /etc/puppetlabs/code/environments


Additional info:
I thought we handled this case and tested it but it's not working on the latest nightly for me.

Comment 3 Bryan Kearney 2018-08-02 20:59:17 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.