Feature #18321

Provide migration to fix cloned roles

Added by Lukas Zapletal over 1 year ago. Updated 9 days ago.

Status:Closed
Priority:Normal
Assignee:Lukas Zapletal
Category:Authorization
Target version:1.15.0
Difficulty: Team Backlog:
Triaged: Fixed in Releases:
Bugzilla link:1378544 Found in Releases:
Pull request:https://github.com/theforeman/foreman/pull/4244

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

Related to Foreman - Bug #16828: Cloned roles should have `builtin` value 0 Closed 10/07/2016

Associated revisions

Revision f505ec3d
Added by Lukas Zapletal over 1 year ago

Fixes #18321 - added migration for builtin roles

History

#1 Updated by Lukas Zapletal over 1 year ago

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

#2 Updated by Lukas Zapletal over 1 year ago

Workaround:

echo "Role.where(:builtin => nil).update_all(:builtin => 0)" | foreman-rake console

#3 Updated by The Foreman Bot over 1 year ago

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

#4 Updated by Lukas Zapletal over 1 year ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Dominic Cleal over 1 year ago

  • Legacy Backlogs Release (now unused) set to 209

#6 Updated by Daniel Lobato Garcia over 1 year ago

  • Target version set to 1.11.0

#7 Updated by Marek Hulán over 1 year ago

  • Bugzilla link set to 1378544

Also available in: Atom PDF