Description of problem: There currently are no input validations, when a user tries to add a new subscription. This means the user can submit any value. However, there seem to be two behaviors following submission of bad values. 1. It appears to submit, then a warning pops up saying "No pools provided". 2. It actually submits the form, says it succeeded, then notifies of the task resulting in a warning state. Version-Release number of selected component (if applicable): Satellite 6.4 Snap 10 How reproducible: Always Steps to Reproduce: 1. Upload a valid manifest, that does not contain all the subscriptions in your account. 2. Navigate to subscriptions, the click "Add Subscriptions" 3. In one of the entitlement fields, enter any range of non-valid inputs. 4. If possible, try to submit the form. Actual results: There is no input validation, and the form submits, resulting in a failed task. Expected results: Input validation warns the user, and stops them from submitting bad data.
It should be noted that behavior #2 (which is more difficult to reliably reproduce) could potentially be causing issues deeper in the system, e.g., candlepin.
Created redmine issue https://projects.theforeman.org/issues/24215 from this bug
Upstream bug assigned to jomitsch
PR merged upstream. Moving to POST.
Verified in Satellite 6.4 Snap 14. I followed my initial reproduction steps, trying a number of different invalid values. The ui caught each of the bad values while they were put in. Additionally, the submit button was disabled while invalid values were present. See attached video for verification.
*** Bug 1599333 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2927