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:
While updating own name/surname, the new string gets displayed in the main menu even when it's invalid (e.g. too long) (see screenshot).
This is not permanent as the form can't be successfully submitted and disappears as soon as user get the name right or cancels the form.
Version-Release number of selected component (if applicable):
6.2.0 snap 8.1
How reproducible:
always
Steps to Reproduce:
1. navigate to My Profile > Edit User
2. update first name/surname to some invalid string
3. hit submit
Actual results:
the name updates in the main menu even if it's not valid
Expected results:
no change is done until form successfully submits the valid data
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/14691 has been closed
-------------
Shlomi Zadok
Applied in changeset commit:2f0bcd5a05b531b28700f638b902bb2c801013c3.
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/RHBA-2016:1501