Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
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