Bug 2167793 - Alternate Content Source do not verify upstream url while refreshing.
Summary: Alternate Content Source do not verify upstream url while refreshing.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Alternate Content Sources
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.13.0
Assignee: satellite6-bugs
QA Contact: David Moore
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-07 14:52 UTC by Akshay Kapse
Modified: 2023-08-03 17:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-16 17:03:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-15781 0 None None None 2023-02-09 15:36:32 UTC

Description Akshay Kapse 2023-02-07 14:52:15 UTC 
Description of problem:
Alternet Content Source do not verify the upstream url and it successsfully completes refresh task without any error or relative message. 


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

How reproducible:
Always

Steps to Reproduce:
1. Install a Satellite 6.13.
2. Create test Alternate Content Source.
Example: 
~~~
URL:        http:test
Subpaths:   test/repo1/,test/repo2/
~~~
3. It gets successfully refreshed without checking whether repositories present or not.

Actual results:
- It gets successfully refreshed without checking whether url is valid or not and repositories/subpaths do exists.
- Dynflow output:
~~~
---
response:
  pulp_href: "/pulp/api/v3/acs/rpm/rpm/972b6753-6fcb-4083-bd57-a939b1797732/"
  pulp_created: !ruby/object:DateTime 2023-02-07 14:41:19.726859000 Z
  name: test-https://<capsule-hostname>:9090-9469
  paths:
  - test/repo1/
  - test/repo2/
  remote: "/pulp/api/v3/remotes/rpm/rpm/fe946446-a47f-46f8-b8c3-886eee483e5c/"
~~~


Expected results:
- Should show some error while refreshing or display some warning message like "404-Not found".

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