Actions
Bug #33251
closedusability issues with updating a repository with invalid data
Status:
Closed
Priority:
Normal
Assignee:
Category:
Ansible Collections
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Description
There are a few usability issues when updating a repository with invalid data:
1. remote update is an async task, but is not being tracked, so invalid data is not noticed
2. We could do better about handling some ansible requirement errors (not a dict, no collections key)
3. We need to do a test remote create at update time before we get to the update run phase, also the error coming back from pulp is ugly
Updated by The Foreman Bot over 3 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/9555 added
Updated by Chris Roberts over 3 years ago
- Target version changed from Katello 4.3.0 to Katello 4.2.0
- Triaged changed from No to Yes
Updated by The Foreman Bot over 3 years ago
- Fixed in Releases Katello 4.3.0 added
Updated by Justin Sherrill over 3 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|821d49fac7f54b17fcfd4a77eafc86e65b92dda5.
Updated by Justin Sherrill over 3 years ago
- Related to Bug #33370: Could not update repository with URL (ISE 500 in logs) when url was not previously set added
Actions