Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Upgrading to 6.5.2 does not trigger db:seed and so any new UpgradeTasks are not being run such as the one required by https://bugzilla.redhat.com/show_bug.cgi?id=1726824


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


How reproducible: Always


Steps to Reproduce:
1. Upgrade from 6.5.1 to 6.5.2
2. Check the Rails console for the UpgradeTasks
> foreman-rake console
> UpgradeTask.all


Actual results: Out from (2) does not show 'katello:upgrades:3.10:update_gpg_key_urls'

Expected results: 'katello:upgrades:3.10:update_gpg_key_urls' should be represented by (2) so that it will be run during the upgrade


Additional info:

*** Bug 1732906 has been marked as a duplicate of this bug. ***

*** Bug 1732907 has been marked as a duplicate of this bug. ***

*** Bug 1732916 has been marked as a duplicate of this bug. ***

Connecting redmine issue https://projects.theforeman.org/issues/27424 from this bug

upstream is merged, moving to POST

Upgraded to latest 6.5.2 SNAP 2 and db:seed ran in the installer correctly:


[ INFO 2019-07-31T00:18:20 main]  Foreman::Rake[db:seed]: Starting to evaluate the resource
[ INFO 2019-07-31T00:18:20 main]  Foreman::Rake[db:seed]: Evaluated in 0.00 seconds
...
[DEBUG 2019-07-31T00:19:30 main] All seed files executed
[DEBUG 2019-07-31T00:19:30 main] foreman-rake db:seed finished successfully!

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-2019:2363