Bug 1690109 - Make Pulp error message more friendly when trying to sync Atomic Host Beta Trees
Summary: Make Pulp error message more friendly when trying to sync Atomic Host Beta Trees
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Kersom
URL:
Whiteboard:
Depends On:
Blocks: 1645017
TreeView+ depends on / blocked
 
Reported: 2019-03-18 19:53 UTC by jcallaha
Modified: 2020-01-06 17:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-06 17:17:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description jcallaha 2019-03-18 19:53:41 UTC 
Description of problem:
When trying to sync the atomic host beta ostree repo, I see the following error:
OST0005: Fetch summary failed. Reason: GLib.Error('Server returned HTTP 404', 'g-io-error-quark', 1)

Version-Release number of selected component (if applicable):
Satellite 6.5.0 Snap 20
This is likely a regression from Snap 19.

How reproducible:
Always

Steps to Reproduce:
1. Upload a manifest that provides Red Hat Enterprise Linux Atomic Host Beta Trees x86_64
2. Enable Red Hat Enterprise Linux Atomic Host Beta Trees x86_64
3. Synchronize Red Hat Enterprise Linux Atomic Host Beta Trees x86_64

Actual results:
OST0005: Fetch summary failed. Reason: GLib.Error('Server returned HTTP 404', 'g-io-error-quark', 1)

Expected results:
The repository syncs successfully 

Additional info:
This also fails with Red Hat Enterprise Linux Atomic Host Preview Trees x86_64
Comment 2 Dennis Kliban 2019-03-20 14:30:58 UTC 
This seems like a problem with the CDN. I've relayed the information to the appropriate team.
Comment 6 Laurie Friedman 2019-03-29 17:49:07 UTC 
@Djordje - We have never released Atomic Host beta.
Comment 7 jcallaha 2019-04-02 14:47:53 UTC 
Removing regression as this looks to have been caused from the content side. 

Additionally, I'd open up the request that if this is not a fault of the pulp end, then the pulp team present the error in a better way.

Something stating what specifically was not available.
Comment 9 Tanya Tereshchenko 2020-01-06 17:17:06 UTC 
There are currently no plans to add this request to Pulp 2 roadmap.
Pulp 2 is in maintenance mode and accepting critical bugs/requests only.
Note You need to log in before you can comment on or make changes to this bug.