Bug 1970960 - Creation of Ansible Collection repo semi-fails on invalid URL
Summary: Creation of Ansible Collection repo semi-fails on invalid URL
Keywords:
Status: CLOSED DUPLICATE of bug 1962132
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-11 14:41 UTC by Marek Hulan
Modified: 2021-06-11 14:50 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-11 14:50:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Marek Hulan 2021-06-11 14:41:49 UTC
Description of problem:

When creating a new repo, if I specify wrong URL the creation fails in the middle with a cryptic error not allowing me to easily start over or even delete the current progress.


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

6.10 / nightly

How reproducible:

100%

Steps to Reproduce:
1. create a repo with invlid/unsupported url like "https://bugzilla.redhat.com/show_bug.cgi?id=1962140" or "https://galaxy.ansible.com/theforeman/foreman"

Actual results:

You get the error notification that is hard to read

"Task 01f9f6dc-c14a-4e10-af16-b76c3519efc7: PulpAnsibleClient::ApiError: Error message: the server returns an error HTTP status code: 400 Response headers: {"Date"=>"Fri, 11 Jun 2021 14:35:19 GMT", "Server"=>"gunicorn/20.0.4", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, POST, HEAD, OPTIONS", "X-Frame-Options"=>"SAMEORIGIN", "Content-Length"=>"114", "Correlation-ID"=>"f4fe9ca8-6b9d-4b24-b9a8-575546119710", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 foreman-nuc2.example.com", "Connection"=>"close"} Response body: {"non_field_errors":["Invalid URL https://bugzilla.redhat.com/show_bug.cgi?id=1962140. Ensure the URL ends '/'."]}"

Fixing the URL does not help now, since the repository is already created, now I'm getting invalid name issue which if I don't know what happend is hard to explain. After changing the name and fixing the URL (adding trailing slash) it's created but I still see the cryptic error toast notification.

Expected results:

It tells me the URL is invalid, bonus points for mentioning the trailing / or even fixing it for me.
It should not create the semi-functional repository that I can't delete.

Comment 1 Marek Hulan 2021-06-11 14:50:36 UTC
already reported, closing

*** This bug has been marked as a duplicate of bug 1962132 ***


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