Bug #31670
closed
Command exceeded timeout while Installer executes foreman-rake db:migrate
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1908237
Installer Clone of the BZ, as the installer should not timeout after 5 minutes.
During an upgrade of 6.7.5 to 6.8.2 (snap 2) the db:migrate step in the installer fails, as it doesn\'t finish in 5 minutes (which is the default timeout for Puppet exec).
[DEBUG 2020-12-04T13:14:09 main] Exec[foreman-rake-db:migrate](provider=posix): Executing \'/usr/sbin/foreman-rake db:migrate\'
[DEBUG 2020-12-04T13:14:09 main] Executing with uid=foreman: \'/usr/sbin/foreman-rake db:migrate\'
[ERROR 2020-12-04T13:19:09 main] Command exceeded timeout
One interesting detail is that Puppet does NOT kill the process, so the db:migrate is running in the background and tries to re-run the installer will result in other, confusing errors (ActiveRecord::ConcurrentMigrationError, Foreman::PermissionMissingException -- the later seems to happen on the "unless" command)
The migration run took roughtly 6 hours on my setup, and I could finish the upgrade just fine after that.
the installer should not assume db:migrate can finish in 5 minutes, this is not realistic.
Updated by The Foreman Bot over 4 years ago
- Status changed from New to Ready For Testing
- Assignee set to Evgeni Golov
- Pull request https://github.com/theforeman/puppet-foreman/pull/915 added
Updated by The Foreman Bot over 4 years ago
- Pull request https://github.com/theforeman/puppet-pulpcore/pull/163 added
Updated by Evgeni Golov over 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman|41f6efae5e38e758aeee663ea4755bbcf0f0fc71.
Updated by Amit Upadhye about 4 years ago
- Subject changed from Command exceeded timeout while Installer executes foreman-rake db:migrate to Command exceeded timeout while Installer executes foreman-rake db:migrate
- Category set to Foreman modules