Actions
Bug #24910
closed
Feature registration does not reliably work in seed tests
Difficulty:
Triaged:
No
Description
After 5.2 upgrade introduced in #24698, problems appeared in foreman_ansible and foreman_openscap that extends seeding. Core seed tests fail since the registration fails, since we're part test invoke rake db:seed. The 5.2 change was that rake db:create loads rails env so the code gets executed too early when DB does not exist yet. We need proper detection method (table_exists?) in core, but meanwhile we agreed on workaround to rescue the exception. Ideally this should be released as 1.6.3
Updated by Marek Hulán over 6 years ago
- Related to Bug #24698: database "test_plugin_matrix-3-dev" does not exist when using `RemoteExecutionFeature.register` with Rails 5.2 added
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_remote_execution/pull/376 added
Updated by Ivan Necas over 6 years ago
- Status changed from Ready For Testing to Closed
Updated by Ivan Necas over 6 years ago
- Fixed in Releases foreman_remote_execution 1.6.3 (Foreman 1.20) added
Actions