Description of problem: Repo discovery feature cannot discover yum repositories because 'Content Default HTTP Proxy' is not used to connect to the upstream URL in Satellite 7.0 The task stops almost immediately after being started and with Success status but based on logs , connectivity to the upstream URL never went through the proxy server. Version-Release number of selected component (if applicable): Satellite 7.0 (Snap 9) (Possibly on Satellite 6.10 as well) How reproducible: Always Steps to Reproduce: 1. Install and Configure a Red Hat Satellite 7 server. 2. Deploy a squid proxy (HTTP or HTTPS) 3. Configure that proxy in Satellite to be used as the Default HTTP proxy for content syncing and manifest operations. 4. Satellite UI -> Content -> Products -> Click Repo Discovery -> "Yum Repositories" --> Put a valid URL in "URL to Discover" field and click on "Discover" Actual results: No discovery of yum repos. Task finishes as soon as it starts without discovering anything at all. ~~ 2022-02-14T05:55:38 [I|app|7ea46644] Started POST "/katello/api/v2/organizations/1/repo_discover" for 10.74.9.134 at 2022-02-14 05:55:38 -0500 2022-02-14T05:55:38 [I|app|7ea46644] Processing by Katello::Api::V2::OrganizationsController#repo_discover as HTML 2022-02-14T05:55:38 [I|app|7ea46644] Parameters: {"id"=>"1", "content_type"=>"yum", "url"=>"http://dogfood.sat.xxx.yyy.com/pulp/repos/Sat6-CI/QA/Satellite_7_0_with_RHEL8_Server/custom/Satellite_Client_Composes/Satellite_Client_RHEL8/", "api_version"=>"v2", "organization"=>{"id"=>"1"}} 2022-02-14T05:55:38 [I|bac|7ea46644] Task {label: , id: 9aa74266-7662-45a6-8342-e75e62d23b63, execution_plan_id: 2fb8304d-23d8-4fa1-8ba0-4c5e9aa17c09} state changed: pending 2022-02-14T05:55:38 [I|bac|7ea46644] Task {label: Actions::Katello::Repository::Discover, id: 9aa74266-7662-45a6-8342-e75e62d23b63, execution_plan_id: 2fb8304d-23d8-4fa1-8ba0-4c5e9aa17c09} state changed: planning 2022-02-14T05:55:38 [I|bac|7ea46644] Task {label: Actions::Katello::Repository::Discover, id: 9aa74266-7662-45a6-8342-e75e62d23b63, execution_plan_id: 2fb8304d-23d8-4fa1-8ba0-4c5e9aa17c09} state changed: planned 2022-02-14T05:55:38 [I|app|7ea46644] Rendering /opt/theforeman/tfm/root/usr/share/gems/gems/katello-4.3.0.2/app/views/katello/api/v2/common/async.json.rabl within katello/api/v2/layouts/resource 2022-02-14T05:55:38 [I|app|7ea46644] Rendered /opt/theforeman/tfm/root/usr/share/gems/gems/katello-4.3.0.2/app/views/katello/api/v2/common/async.json.rabl within katello/api/v2/layouts/resource (Duration: 15.1ms | Allocations: 7589) 2022-02-14T05:55:38 [I|app|7ea46644] Completed 202 Accepted in 129ms (Views: 15.9ms | ActiveRecord: 22.5ms | Allocations: 30002) 2022-02-14T05:55:38 [I|bac|7ea46644] Task {label: Actions::Katello::Repository::Discover, id: 9aa74266-7662-45a6-8342-e75e62d23b63, execution_plan_id: 2fb8304d-23d8-4fa1-8ba0-4c5e9aa17c09} state changed: running 2022-02-14T05:55:38 [I|bac|7ea46644] Task {label: Actions::Katello::Repository::Discover, id: 9aa74266-7662-45a6-8342-e75e62d23b63, execution_plan_id: 2fb8304d-23d8-4fa1-8ba0-4c5e9aa17c09} state changed: stopped result: success ~~ No access to squid server from satellite to connect to upstream URL of that yum repo. Expected results: Repo Discovery should work fine and use the "Content Default HTTP Proxy" Additional info: NOTE: Docker type repo discovery works fine under same circumstances.
Is this a regression from Satellite 6.10?
Hello Brad, Via proxy, This feature: Works fine on Satellite 6.9 (tested on 6.9.7) Does not work on Satellite 6.10 and 7.0 as explained in the description. Best Regards, Sayan
This was fixed as part of https://bugzilla.redhat.com/show_bug.cgi?id=2046337 Moving this to POST
Verified in Satellite 6.11 Snap 18 Steps: 1. Setup squid proxy 2. Add squid proxy to HTTP proxies 3. Set that as the content proxy 4. Discover https://fixtures.pulpproject.org/ Results: Repo discovery worked perfectly fine. In the current version of pulp fixtures, 65 repos were discovered. See attached screenshot.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5498