Bug #10466
closed
Proxy registration puppet error is not clear
Added by Lukas Zapletal over 9 years ago.
Updated over 6 years ago.
Description
We show 422 error on unsuccessful requests, we should print nicer errors.
- Status changed from New to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 35
- Related to Bug #11331: foreman_smartproxy: failed to call refresh: missing param 'id' in parameters after ensure failure added
- Related to Bug #14060: Error message unclear when capsule fails to register (Could not set 'present on ensure: 422 Unprocessable Entity) added
Also available in: Atom
PDF