Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Since we've moved to using the UpgradeTask model[1] of Foreman via seeds[2] we need to be absolutely certain that db:seed runs during installation and upgrades so that all of the upgrade tasks are executed. We can't rely on the potential side-effect of other actions during installation or upgrade to do the seed for us.



[1] https://github.com/theforeman/foreman/pull/5780/files
[2] https://github.com/Katello/katello/blob/master/db/seeds.d/111-upgrade_tasks.rb

Created from redmine issue https://projects.theforeman.org/issues/27424

*** This bug has been marked as a duplicate of bug 1732921 ***