Project

General

Profile

Actions

Bug #6868

closed

Login in foreman

Added by Douglas Brancaglion almost 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Authentication
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hi, i use mysqlDB in my foreman setup, but i receive that messages when i try to login:

ActiveRecord::AssociationTypeMismatch
Role(#56476060) expected, got NilClass(#7624920)
app/models/user.rb:206:in `block in post_successful_login'
app/models/concerns/foreman/thread_session.rb:72:in `as'
app/models/user.rb:203:in `post_successful_login'
app/models/user.rb:194:in `try_to_login'
app/controllers/users_controller.rb:72:in `login'
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
lib/middleware/catch_json_parse_errors.rb:9:in `call'

Actions #1

Updated by Ohad Levy almost 10 years ago

  • Status changed from New to Feedback

Can you try running foreman-rake db:migrate followed by a foreman-rake db:seed?

Actions #2

Updated by Douglas Brancaglion almost 10 years ago

I had not run the rake db: seed, after that everything was ok!

But I still have another problem: The foreman recognizes the class created in the / etc / puppet / environments / production / modules / likewise

But I edit the node for foreman and likewise include the class, but when I run the puppet client it gives this error message:

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class is likewise client.mydomain.domain on node client.mydomain.domain
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Actions #3

Updated by Douglas Brancaglion almost 10 years ago

Ohad, runs like a charm now! please disregard the last message (module topology)!

Tks

Actions #4

Updated by Dominic Cleal almost 10 years ago

  • Status changed from Feedback to Resolved

Glad it's working!

Actions

Also available in: Atom PDF