Feature #15779
closedMake report, puppet classes and environments importing asynchronous using foreman-tasks
Description
There are already 90% done on foreman-tasks side so we can just move it to core. For importing puppet objects it might make sense to keep synchronous way still available.
Updated by Marek Hulán over 8 years ago
- Blocked by Bug #15778: Can't use process_success Foreman method in API controllers on DynflowTask added
Updated by Marek Hulán over 8 years ago
- Blocks Refactor #15770: Move reports import and puppet class/environments importing to Foreman core added
Updated by Marek Hulán over 8 years ago
- Blocks Feature #15780: Support async importing from puppet master added
Updated by The Foreman Bot over 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3670 added
Updated by Marek Hulán about 8 years ago
- Related to Feature #7514: add foreman tasks into core added
Updated by Ivan Necas about 8 years ago
- Blocked by Feature #17283: In thread executor for testing inside transactions added
Updated by Ivan Necas almost 8 years ago
- Blocked by Bug #17361: `rake db:drop db:create db:migrate` doesn't migrate plugins added
Updated by Ivan Necas almost 8 years ago
- Related to Feature #17467: Configure tasks by default added
Updated by Marek Hulán almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset eb371ca33dcdd7a4f71d3cda0cfcad701cd3ae7e.
Updated by Dominic Cleal almost 8 years ago
- Related to Bug #17482: Incorrect concatentation of environment import strings to form sentences added
Updated by Ewoud Kohl van Wijngaarden almost 8 years ago
- Related to Refactor #17483: Async HTTP API calls should return code 202 Accepted instead of 201 Created added
Updated by Dominic Cleal almost 8 years ago
- Translation missing: en.field_release set to 189
Updated by Ohad Levy almost 8 years ago
- Related to Bug #17495: Align foreman configuration report expiry with Task expiry added
Updated by The Foreman Bot almost 8 years ago
- Pull request https://github.com/theforeman/foreman/pull/4075 added
Updated by Dominic Cleal almost 8 years ago
- Translation missing: en.field_release changed from 189 to 209
Moving due to continuing build/test failures.
Updated by Dominic Cleal almost 8 years ago
- Related to Bug #17575: "Failed importing of report" error printed to stderr when running tests added
Updated by Marek Hulán almost 8 years ago
Could you please be more specific? What is failing? The rpm packaging PR was awaiting the core PR to be merged, which is in now and the packaging PR is green atm. Thank you.
Updated by Dominic Cleal almost 8 years ago
Debian package tests of foreman
have been failing since 25/11 (e.g. http://ci.theforeman.org/job/systest_foreman/11422/) as the dependency isn't correctly packaged. RPM builds of foreman
have been failing since the same as bundler.d/foreman_tasks.rb is unpackaged.
The packaging PRs were and are still outstanding - if they were finished, worked and tested then it might have been feasible, but they were not.
Updated by The Foreman Bot almost 8 years ago
- Pull request https://github.com/theforeman/foreman-packaging/pull/1436 added
Updated by The Foreman Bot almost 8 years ago
- Pull request https://github.com/theforeman/foreman-packaging/pull/1437 added
Updated by Ohad Levy almost 8 years ago
- Related to Bug #17871: Circular dependency detected while autoloading constant ConfigReportStatusCalculator added
Updated by The Foreman Bot almost 8 years ago
- Pull request https://github.com/theforeman/foreman-packaging/pull/1493 added
Updated by The Foreman Bot almost 8 years ago
- Pull request https://github.com/theforeman/foreman/pull/4217 added