Bug 1559108
Summary: | 6.3 upgrade causes missing Templates history | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Sean O'Keeffe <sokeeffe> | |
Component: | Provisioning Templates | Assignee: | satellite6-bugs <satellite6-bugs> | |
Status: | CLOSED ERRATA | QA Contact: | Ranjan Kumar <rankumar> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.3.0 | CC: | graham.dougan, mhulan, pcreech, rankumar, sjagtap, smane, tbhowmik | |
Target Milestone: | Unspecified | Keywords: | Regression, Triaged | |
Target Release: | Unused | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | foreman-1.15.6.41-1,foreman-1.15.6.44-1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1572301 (view as bug list) | Environment: | ||
Last Closed: | 2018-06-19 20:17:00 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Sean O'Keeffe
2018-03-21 17:19:32 UTC
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 Steps: 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 foreman-1.15.6.45-1.el7sat.noarch 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. https://access.redhat.com/errata/RHBA-2018:1950 |