Bug 2208013
| Summary: | pulpcore_export_destination value not added to allowed export path for content exports in Satelite | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Taft Sanders <tasander> |
| Component: | Inter Satellite Sync | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED NOTABUG | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.12.3 | CC: | ahumbe, jpasqual, paji, rlavi |
| Target Milestone: | Unspecified | Keywords: | WorkAround |
| 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: | 2023-06-26 14:35:57 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: | |||
I think this is expected if you don't previously add an additional export path to pulp. Do it like this (to be persistent): ~~~ satellite-installer --foreman-proxy-content-pulpcore-additional-export-paths /satellite_exports ~~~ Then you should be able to modify the configuration on the webUI to match it. Partha, Is it expected that a user should perform both an installer command and Setting update to change the location of the export path? Is it necessary to have both? If so, should this be a documentation bugzilla or notabug? This issue is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=2158186 and the outcome of that was there NOTABUG If you are setting your new default path to be something that is not in the allowed_export paths you would need to run installer and restart. Since pulp services require that. Recommend going through the comments in that bug. (In reply to Partha Aji from comment #3) > This issue is a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=2158186 > and the outcome of that was there NOTABUG > > If you are setting your new default path to be something that is not in the > allowed_export paths you would need to run installer and restart. Since pulp > services require that. > > Recommend going through the comments in that bug. Based on the comments from Bugzilla 2158186, I'm closing this out as not a bug. I have filed an RFE instead to have the installer option '--foreman-proxy-content-pulpcore-additional-export-paths' set the setting 'pulpcore_export_destination' to the new value provided by default. |
Description of problem: Setting a custom export location in Satellite WebUI > Administrator > Settings > Content > pulpcore_export_destination does not work Version-Release number of selected component (if applicable): satellite-6.12.3-1.el8sat.noarch How reproducible: Every time Steps to Reproduce: 1. Sync a repository on immediate sync policy 2. Set the pulpcore_export_destination to any destination pulp can read and write to, like /tmp 3. Export the repository Actual results: [root@bombsat612 ~]# hammer content-export complete repository --id 6 [...................................................................................................................................................................] [100%] Error: Error message: the server returns an error HTTP status code: 400 Response headers: {"Date"=>"Wed, 17 May 2023 16:24:38 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, POST, HEAD, OPTIONS", "X-Frame-Options"=>"DENY", "Content-Length"=>"171", "X-Content-Type-Options"=>"nosniff", "Referrer-Policy"=>"same-origin", "Correlation-ID"=>"80d36b95-7540-4268-adb0-1db9302f56be", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 bombsat612.d.sysmgmt.cee.redhat.com", "Connection"=>"close"} Response body: {"path":["Path '/tmp/Default_Organization/Export-Red_Hat_Satellite_Client_6_for_RHEL_7_Server_RPMs_x86_64-6/6.0/2023-05-17T12-24-38-04-00' is not an allowed export path"]} Expected results: [root@bombsat612 ~]# hammer content-export complete repository --id 6 [...................................................................................................................................................................] [100%] Generated /tmp/Default_Organization/Export-Red_Hat_Satellite_Client_6_for_RHEL_7_Server_RPMs_x86_64-6/7.0/2023-05-17T12-25-50-04-00/metadata.json Additional info: This setting's value doesn't appear to be taken into consideration even with making the code change for a known issue where pulp doesn't get the polling interval and bulk_load_size values from settings (Bugzilla 2121288). A simple work-around is to add the path to the /etc/pulp/settings.py parameter 'ALLOWED_EXPORT_PATHS' like the following: BEFORE: ALLOWED_EXPORT_PATHS = ["/var/lib/pulp/exports"] AFTER: ALLOWED_EXPORT_PATHS = ["/var/lib/pulp/exports","/tmp"] Then restart the pulpcore services: # systemctl restart pulpcore* The export worked after making this change: [root@bombsat612 ~]# vim /etc/pulp/settings.py [root@bombsat612 ~]# systemctl restart pulpcore* [root@bombsat612 ~]# hammer content-export complete repository --id 6 [...................................................................................................................................................................] [100%] Generated /tmp/Default_Organization/Export-Red_Hat_Satellite_Client_6_for_RHEL_7_Server_RPMs_x86_64-6/7.0/2023-05-17T12-25-50-04-00/metadata.json