Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:
=======================
Starting with at least the subscription-manager-gui-1.16.4-1.git.0.c250102.el6.x86_64 code base, when some actions are followed up by dialogs, the dialog boxes are info dialogs rather than error dialogs.
The inconsistency between popping up info or dialog windows breaks automation tests which assumes that if an info dialog pops up, things are ok. Here are some examples:
Register with an empty username
Register with an empty password
Register without a system name
However, some fields when missing any text throw an error dialog. For example, failing to enter any text for the subscription server results in an error dialog box. Also, entering incorrect user/pw combo results in an error dialog.
However, missing fields should be treated the same as errors...meaning that the user has entered incorrect information (as is correctly done when no subscription URL is provided).
Version-Release number of selected component (if applicable):
============================================================
[root@rhel67-stoner-test ~]# rpm -qa | grep subscription
subscription-manager-gui-1.16.4-1.git.0.c250102.el6.x86_64
subscription-manager-1.16.4-1.git.0.c250102.el6.x86_64
subscription-manager-firstboot-1.16.4-1.git.0.c250102.el6.x86_64
subscription-manager-migration-1.16.4-1.git.0.c250102.el6.x86_64
subscription-manager-migration-data-2.0.22-1.git.0.4260892.el6.noarch
subscription-manager-plugin-container-1.16.4-1.git.0.c250102.el6.x86_64
How reproducible:
=================
Always
Steps to Reproduce:
1. In the GUI, leave the username blank
2. Notice the Icon is a light bulb indicating an info dialog box
Actual results:
An information dialog box shows up to inform user of problem
Expected results:
An error dialog box should show up to inform user of problem
Additional info:
Created attachment 1096833[details]
information dialog when username is blank
Screenshot of an information dialog that is presented when the user leaves the username field blank
commit c89df8add6d34a86eff0288fe7abee672902dcab
Author: William Poteat <wpoteat>
Date: Mon Jan 4 12:02:08 2016 -0500
1283749: Upgrade the dialogs to error when required fields are blank.
Also corrected a couple of stylish issues.
The dialogs are still showing up as Informational type dialogs (see attached screenshot). Not only does the dialog still show up as an Informational type dialog but the locator name still says "Informational" (see attached screenshot)
Ultimately, the way that we determine if a dialog is an error type dialog or not is by looking at the locator name. The ldtp tool that we use has a property called "class" for a window, but it always returns "alert" whether it's an info type dialog, or error type dialog.
Moving bug to verified state as I see the error dialogues while attempting to register using blank username and password
[root@dhcp35-71 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.9.51.20-1
subscription management rules: 5.15.1
subscription-manager: 1.18.3-1.el6
python-rhsm: 1.18.4-1.el6
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://rhn.redhat.com/errata/RHSA-2017-0698.html