Bug 2053970

Summary: Upgrade to Red Hat Satellite 7.0 fails at db:migrate step with error "undefined local variable or method `type' for #<Katello::CdnConfiguration:0x00000000153c6198>"
Product: Red Hat Satellite Reporter: Satyajit Das <sadas>
Component: Subscription ManagementAssignee: Partha Aji <paji>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: lpramuk, osousa, pcreech
Target Milestone: 6.11.0Keywords: Triaged, UpgradeBlocker, Upgrades
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-4.3.0.5-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 14:33:17 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 Satyajit Das 2022-02-13 16:34:32 UTC 
Description of problem:

Upgrade to Red Hat Satellite 7.0 fails at db:migrate step with error "undefined local variable or method `type' for #<Katello::CdnConfiguration:0x00000000153c6198>"


Version-Release number of selected component (if applicable):

satellite-7.0

How reproducible:

100%

Steps to Reproduce:

Upgrading satellite from 6.10.2 to 7.0 fails executing [foreman-rake-db:migrate] with exception:-

Actual results:

[ERROR ] [configure] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: change from 'notrun' to ['0'] failed: '/usr/sbin/foreman-rake db:migrate' returned 1 instead of one of [0]

Expected results:

During the upgrade foreman-rake-db:migrate should execute successfully.


Additional info:
Comment 4 Partha Aji 2022-02-15 20:51:56 UTC 
Connecting redmine issue https://projects.theforeman.org/issues/34455 from this bug
Comment 5 Lukas Pramuk 2022-02-17 10:44:23 UTC 
I hit this too with customer DB, errors show that it happens during db:migrate not db:seed
Comment 6 Bryan Kearney 2022-02-17 16:07:00 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34455 has been resolved.
Comment 8 Lukas Pramuk 2022-02-25 09:40:27 UTC 
VERIFIED.

@Satellite 7.0.0 Snap11
tfm-rubygem-katello-4.3.0.7-1.el7sat.noarch

# satellite-maintain upgrade run --target-version 7.0 -w repositories-validate,repositories-setup -y
...

Running Migration scripts to Satellite 7.0
================================================================================
Setup repositories:                                                   [SKIPPED]
--------------------------------------------------------------------------------
Unlock packages:                                                      [OK]
--------------------------------------------------------------------------------
Update package(s) :                                                   [OK]
--------------------------------------------------------------------------------
Procedures::Installer::Upgrade:                                       [OK]
--------------------------------------------------------------------------------
Execute upgrade:run rake task:                                        [OK]
--------------------------------------------------------------------------------
...

Upgrade finished.

>>> db:migrate step finishes successfully - 2022-02-25 04:19:32 [INFO  ] [configure] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/returns: executed successfully
Comment 13 errata-xmlrpc 2022-07-05 14:33:17 UTC 
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 (Moderate: Satellite 6.11 Release), 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/RHSA-2022:5498