Project

General

Profile

Actions

Bug #4832

closed

Deleting user ends up with traceback

Added by Jiří Mikulka about 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

When one wants to delete an user on <hostname>/users page, it ends up with a traceback:

[...]
ActiveRecord::StatementInvalid
PGError: ERROR: column katello_content_view_histories.user_id does not exist LINE 1: ...s".* FROM "katello_content_view_histories" WHERE "katello_c... ^ : SELECT "katello_content_view_histories".* FROM "katello_content_view_histories" WHERE "katello_content_view_histories"."user_id" = 3
app/controllers/users_controller.rb:55:in `destroy'
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
lib/middleware/catch_json_parse_errors.rb:9:in `call'
[...]

And the user is not deleted, but the account is still active and can be used for logging in.

Actions #1

Updated by Dominic Cleal about 10 years ago

  • Project changed from Foreman to Katello
  • Subject changed from Deleteing user ends up with traceback to Deleting user ends up with traceback
  • Triaged set to No
Actions #2

Updated by Jiří Mikulka about 10 years ago

Ha! I've just discovered that it's just enough to wait 15 minutes to make it happen! I guess that deleting few entries in the database must be fast, no one wants to spend 15 minutes waiting for such trivial action to be completed.

Jiří Mikulka wrote:

When one wants to delete an user on <hostname>/users page, it ends up with a traceback:

[...]
ActiveRecord::StatementInvalid
PGError: ERROR: column katello_content_view_histories.user_id does not exist LINE 1: ...s".* FROM "katello_content_view_histories" WHERE "katello_c... ^ : SELECT "katello_content_view_histories".* FROM "katello_content_view_histories" WHERE "katello_content_view_histories"."user_id" = 3
app/controllers/users_controller.rb:55:in `destroy'
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'
lib/middleware/catch_json_parse_errors.rb:9:in `call'
[...]

And the user is not deleted, but the account is still active and can be used for logging in.

Actions #3

Updated by Justin Sherrill about 10 years ago

  • translation missing: en.field_release set to 13
Actions #4

Updated by Eric Helms almost 10 years ago

  • Status changed from New to Closed
  • Triaged changed from No to Yes

Tested this locally by creating a user and then deleting them and was not able to reproduce this issue.

Actions

Also available in: Atom PDF