Bug 1107696 - Plugin permissions are skipped during migration from old to new system
Summary: Plugin permissions are skipped during migration from old to new system
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-10 12:52 UTC by Bryan Kearney
Modified: 2019-09-26 18:13 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-01 10:13:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5689 0 None None None 2016-04-22 15:40:12 UTC

Description Bryan Kearney 2014-06-10 12:52:08 UTC 
Plugin initializer is loaded only once when running multiple migrations. Since plugin permissions are ignored (permissions table does not exist yet) they are not created in database and permission migration can't migrate them. Therefore we must find all plugin permission during permission migration and create them before that.
Comment 1 Bryan Kearney 2014-06-10 12:52:10 UTC 
Created from redmine issue http://projects.theforeman.org/issues/5689
Comment 2 Bryan Kearney 2014-06-10 12:52:20 UTC 
Upstream bug assigned to mhulan
Comment 3 Bryan Kearney 2014-06-10 13:04:20 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/5689 has been closed
Comment 6 Tazim Kolhar 2014-08-27 12:13:12 UTC 
please provide verification steps
Comment 7 Dominic Cleal 2014-09-01 10:13:57 UTC 
It tests upgrades from older versions of Foreman with plugins installed to the current version.  It doesn't make sense to test upgrades *to* Satellite 6.0, so closing.  I've just verified that the code is indeed included.
Note You need to log in before you can comment on or make changes to this bug.