Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2217525

Summary:	[RFE]: Update Settings pulpcore_export_destination with new value supplied by installer argument "--foreman-proxy-content-pulpcore-additional-export-paths"
Product:	Red Hat Satellite	Reporter:	Taft Sanders <tasander>
Component:	Repositories	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.2	CC:	egolov, ehelms, rlavi, saydas, thadzhie
Target Milestone:	Unspecified	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:23:11 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:
Embargoed:

Description Taft Sanders 2023-06-26 14:28:41 UTC

Description of problem:
Upon running the installer to add a new destination for pulp exports an additional step of setting the pulpcore_export_destination Setting via hammer or the WebUI must be set in order to use the new export path.
This request is to update this setting value to the new value upon a successful completion of running the installer with this option.

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


How reproducible:
Every time

Steps to Reproduce:
1. Run the installer with the '--foreman-proxy-content-pulpcore-additional-export-paths' option to specify a new export location.
2. Try to export and watch it export to the previously set location
3. Update the setting 'pulpcore_export_destination' to the new location and export again.
4. Export will export to the new location

Actual results:
Pulp will export to the previously set location listed in the Satellite settings

Expected results:
Use 1 action to change the export location to simplify workflow


Additional info:
This RFE comes from bugs previously filed:
https://bugzilla.redhat.com/show_bug.cgi?id=2208013
https://bugzilla.redhat.com/show_bug.cgi?id=2158186
https://access.redhat.com/solutions/7013903

Comment 1 Taft Sanders 2023-06-26 14:46:20 UTC

A Bugzilla for the documentation has also been opened to add the current procedure to the documentation. Should the result of this RFE be implemented, please reopen Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2217528 to have the procedure updated.

Comment 2 Sayan Das 2023-06-26 14:55:00 UTC

+1 

The less confusion we create, the better the user experience would be. 

If What Taft requested is not possible to implement for any reason then , My alternate proposal is 

* Have the installer executed by the end-user to allow a new location as the export_path

* As far as the setting pulpcore_export_destination goes, at the backend

   * It should somehow read the pulp config and get all the allowed export_paths
   * List then as selectable options

In that way, some manual errors due to typo ( as the value of pulpcore_export_destination )  can be avoided

Comment 3 Eric Helms 2024-06-06 16:23:11 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.