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.

Bug 1384182

Summary: Unable to view errata page as a user that doesn't have a name and email defined
Product: Red Hat Satellite Reporter: jcallaha
Component: WebUIAssignee: satellite6-bugs <satellite6-bugs>
WebUI sub component: Katello QA Contact: Katello QA List <katello-qa-list>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: mhulan
Version: 6.2.3   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-15 11:34:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jcallaha 2016-10-12 18:26:27 UTC
Description of problem:
When attempting to view the errata page as a user, who didn't have a name or email address listed, I see the following error message.

Oops, we're sorry but something went wrong No route matches {:action=>"edit", :bastion_page=>"errata", :controller=>"users", :id=>#<User id: 9, login: "testuser", firstname: "", lastname: "", mail: "", admin: false, last_login_on: "2016-10-12 17:49:18", auth_source_id: 1, created_at: "2016-10-12 17:20:23", updated_at: "2016-10-12 17:49:18", password_hash: "e0db5439af0dec77e634f4a4f7848ab7cae207eb", password_salt: "306f342ad07c248447a56bb2eb072664303ab5b3", locale: nil, avatar_hash: nil, default_organization_id: 1, default_location_id: nil, lower_login: "testuser", mail_enabled: true, timezone: "">} missing required keys: []

Version-Release number of selected component (if applicable):
Satellite 6.2.3 Snap 3

How reproducible:
Always

Steps to Reproduce:
1. Create a new user with the permissions to view the errata page. Ensure that you do not fill out the name and email address.
2. Navigate to Content -> Errata

Actual results:
Unable to navigate to the page. The following error is seen:
Oops, we're sorry but something went wrong No route matches {:action=>"edit", :bastion_page=>"errata", :controller=>"users", :id=>#<User id: 9, login: "testuser", firstname: "", lastname: "", mail: "", admin: false, last_login_on: "2016-10-12 17:49:18", auth_source_id: 1, created_at: "2016-10-12 17:20:23", updated_at: "2016-10-12 17:49:18", password_hash: "e0db5439af0dec77e634f4a4f7848ab7cae207eb", password_salt: "306f342ad07c248447a56bb2eb072664303ab5b3", locale: nil, avatar_hash: nil, default_organization_id: 1, default_location_id: nil, lower_login: "testuser", mail_enabled: true, timezone: "">} missing required keys: []

Expected results:
Navigation should be successful.

Comment 1 jcallaha 2016-10-12 18:27:51 UTC
An easy workaround is to add a name and email address to the user.

Comment 3 Marek Hulan 2017-09-15 11:34:52 UTC
Closing as a duplicate, tested the fix from there and it fixes the issue for errata page too.

*** This bug has been marked as a duplicate of bug 1435414 ***