Project

General

Profile

Actions
Copy link

Feature #18321

closed

Provide migration to fix cloned roles

Added by Lukas Zapletal about 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Users, Roles and Permissions
Target version:
1.15.0
Difficulty:
Triaged:
Bugzilla link:
1378544
Pull request:
https://github.com/theforeman/foreman/pull/4244
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

When role was cloned, it was created with incorrect builtin value causing issues. This was fixed in #16828 but no migration was provided to fix already cloned records:

Role.where(:builtin => nil).update_all(:builtin => 0)

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #16828: Cloned roles should have `builtin` value 0ClosedSwapnil Abnave10/07/2016Actions
Actions
Copy link
 #1

Updated by Lukas Zapletal about 7 years ago

  • Related to Bug #16828: Cloned roles should have `builtin` value 0 added
Actions
Copy link
 #2

Updated by Lukas Zapletal about 7 years ago

Workaround:

echo "Role.where(:builtin => nil).update_all(:builtin => 0)" | foreman-rake console
Actions
Copy link
 #3

Updated by The Foreman Bot about 7 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Lukas Zapletal
  • Pull request https://github.com/theforeman/foreman/pull/4244 added
Actions
Copy link
 #4

Updated by Lukas Zapletal about 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #5

Updated by Dominic Cleal about 7 years ago

  • translation missing: en.field_release set to 209
Actions
Copy link
 #6

Updated by Daniel Lobato Garcia about 7 years ago

  • Target version set to 1.11.0
Actions
Copy link
 #7

Updated by Marek Hulán about 7 years ago

  • Bugzilla link set to 1378544
Actions
Copy link

Also available in: Atom PDF