Bug #31985
closed
Template sync fails with unclear error
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1925258
Description of problem:
Export Template sync fails with error below:
Oh no! Something went wrong while submitting the form, the server returned the following error: Error: Request failed with status code 422
Version-Release number of selected component (if applicable):
2.3
How reproducible:
Always
Steps to Reproduce:
1. Hosts -> Sync Templates
2. Select Action type as Export
3. Click Submit
4. You will land to new Page "No Template Sync Result", Click Sync Templates
5. You will see error message as below:
Oh no! Something went wrong while submitting the form, the server returned the following error: Error: Request failed with status code 422
Actual results:
Error received:
Oh no! Something went wrong while submitting the form, the server returned the following error: Error: Request failed with status code 422
Expected results:
Proper error message with clear distincion what went wrong as
Error! Please specify a branch when exporting into a git repo
Updated by Ondřej Ezr almost 4 years ago
- Related to Bug #31848: ForemanForm (react) has a regression which fails to show errors after submission added
Updated by Ondřej Ezr almost 4 years ago
- Related to Bug #31798: react forms create toast notifications with unclear error description added
Updated by The Foreman Bot almost 4 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ondřej Ezr
- Pull request https://github.com/theforeman/foreman_templates/pull/151 added
Updated by The Foreman Bot almost 4 years ago
- Fixed in Releases foreman_templates 10.0.0 added
Updated by Ondřej Pražák almost 4 years ago
- Subject changed from Template sync fails with unclear error to Template sync fails with unclear error
- Status changed from Ready For Testing to Closed
- Fixed in Releases foreman_templates 9.0.2 added
- Fixed in Releases deleted (
foreman_templates 10.0.0)
Updated by Ondřej Pražák almost 4 years ago
- Related to Bug #32113: Fix server error propagation added