Red Hat Bugzilla – Bug 1559108
6.3 upgrade causes missing Templates history
Last modified: 2018-06-19 16:17:34 EDT
Description of problem:
After upgrading to 6.3 i see no history for my provisioning template
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. build 6.2
2. create custom Provisioning Template
3. makes a change to that Template
4. check history tab for you change
5. Upgrade to 6.3
6. go to the history tab and no history will be displayed
no history is displayed
All previous history is displayed
It seems in 6.2 they were saved in the audit table as `:auditable_type => Template` whereas 6.3 they look like they are `:auditable_type => ProvisioningTemplate` and there has been no migration.
irb(main):028:0* Audit.descending.where(:auditable_id => 111, :auditable_type => Template, :action => 'update').count
irb(main):029:0> Audit.descending.where(:auditable_id => 111, :auditable_type => Template, :action => 'update').first.created_at
=> Fri, 16 Mar 2018 15:46:56 UTC +00:00
irb(main):030:0> Audit.descending.where(:auditable_id => 111, :auditable_type => ProvisioningTemplate, :action => 'update').count
irb(main):031:0> Audit.descending.where(:auditable_id => 111, :auditable_type => ProvisioningTemplate, :action => 'update').first.created_at
=> Wed, 21 Mar 2018 16:27:25 UTC +00:00
We upgraded on the morning of 21 Mar 2018
This looks like to be caused by https://github.com/theforeman/foreman/commit/5908bf418d28c57dcdc4d2e01ccf3253c0e8a81a I'm not sure why that migration was written like that? Or if they *should* be stored as ProvisioningTemplates or Templates?
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22984 has been resolved.
Verified on satellite 6.3.2 2.0
1. Build Satellite 6.3.1
2. Created new provisioning template
3. modified the provisioning template
4. Upgraded Satellite to 6.3.2 2.0
[root@rhel7-sat62-4 migrate]# rpm -qa | grep foreman
I can see Provisioning template history after upgrade to satellite 6.3.2 2.0
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.