Feature #18321

Provide migration to fix cloned roles

Added by Lukas Zapletal 11 months ago. Updated 10 months ago.

Status:Closed
Priority:Normal
Assigned To:Lukas Zapletal
Category:Authorization
Target version:Team Daniel - Iteration 9
Difficulty: Bugzilla link:1378544
Found in release: Pull request:https://github.com/theforeman/foreman/pull/4244
Story points-
Velocity based estimate-
Release1.15.0Release relationshipAuto

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 11 months ago

Fixes #18321 - added migration for builtin roles

History

#1 Updated by Lukas Zapletal 11 months ago

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

#2 Updated by Lukas Zapletal 11 months ago

Workaround:

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

#3 Updated by The Foreman Bot 11 months ago

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

#4 Updated by Lukas Zapletal 11 months ago

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

#5 Updated by Dominic Cleal 11 months ago

  • Release set to 1.15.0

#6 Updated by Daniel Lobato Garcia 10 months ago

  • Target version set to Team Daniel - Iteration 9

#7 Updated by Marek Hulán 10 months ago

  • Bugzilla link set to 1378544

Also available in: Atom PDF