Bug #7900: Bastion pages fail to load due to error in CurrentUser JSON - Katello - Foreman

Bug #7900

Bastion pages fail to load due to error in CurrentUser JSON

Added by Eric Helms over 7 years ago. Updated almost 4 years ago.

Status:

Closed

Priority:

Urgent

Assignee:

Eric Helms

Category:

Web UI

Target version:

Katello 2.1

Difficulty:

easy

Triaged:

Yes

Bugzilla link:

Pull request:

https://github.com/Katello/katello/pull/4733

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Uncaught SyntaxError: Unexpected token
angular.js?body=1:1037
Uncaught Error: [$injector:modulerr] Failed to instantiate module Bastion.activation-keys due to:
Error: [$injector:modulerr] Failed to instantiate module Bastion due to:
Error: [$injector:unpr] Unknown provider: BastionConfig
http://errors.angular...<omitted>...1)

Related issues

Associated revisions

Revision 7f6af41a (diff)
Added by Eric Helms over 7 years ago

Fixes #7900: Bastion pages couldn't load due to unparseable User.to_json

A change to the User model led some fields to be unparseable when
User.current.to_json is done within the layout. This reduces the fields
to only those specifically needed by the UI.

Revision 18a89203
Added by Eric Helms over 7 years ago

Merge pull request #4733 from ehelms/fixes-7900

Fixes #7900: Bastion pages couldn't load due to unparseable User.to_json