Issue #683
closedPulp throws away validation error information from distributors
Description
Description of problem:
If there are validation errors, Pulp catches it and raises an unhelpful error.
How reproducible:
Always
Steps to Reproduce:
1. Create a distributor config that will fail validation, like a docker repo with a capital letter in the repo-registry-id
Actual results:
Pulp exception occurred: PulpDataException
Expected results:
A helpful error.
Additional info:
Fixed with:
https://github.com/pulp/pulp/pull/1487/
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Description:
Packages to be added:
Comps group:
Default:
Mandatory:
Visible:
Multi-lib:
Need to be present for arches:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Description:
Packages to be added:
Comps group:
Default:
Mandatory:
Visible:
Multi-lib:
Need to be present for arches:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Description:
Packages to be added:
Comps group:
Default:
Mandatory:
Visible:
Multi-lib:
Need to be present for arches:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Description:
Packages to be added:
Comps group:
Default:
Mandatory:
Visible:
Multi-lib:
Need to be present for arches:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Document URL:
Section Number and Name:
Describe the issue:
Suggestions for improvement:
Additional information:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Description:
Packages to be added:
Comps group:
Default:
Mandatory:
Visible:
Multi-lib:
Need to be present for arches:
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
+ This bug was cloned from Bugzilla Bug #1187200 +
Related issues