Feature #15779
closed
Make report, puppet classes and environments importing asynchronous using foreman-tasks
Added by Marek Hulán almost 8 years ago.
Updated almost 6 years ago.
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.
- Blocked by Bug #15778: Can't use process_success Foreman method in API controllers on DynflowTask added
- Blocks Refactor #15770: Move reports import and puppet class/environments importing to Foreman core added
- Blocks Feature #15780: Support async importing from puppet master added
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3670 added
- Blocked by Feature #17283: In thread executor for testing inside transactions added
- Blocked by Bug #17361: `rake db:drop db:create db:migrate` doesn't migrate plugins added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #17482: Incorrect concatentation of environment import strings to form sentences added
- Related to Refactor #17483: Async HTTP API calls should return code 202 Accepted instead of 201 Created added
- translation missing: en.field_release set to 189
- Target version set to 1.4.4
- Related to Bug #17495: Align foreman configuration report expiry with Task expiry added
- Pull request https://github.com/theforeman/foreman/pull/4075 added
- translation missing: en.field_release changed from 189 to 209
Moving due to continuing build/test failures.
- Related to Bug #17575: "Failed importing of report" error printed to stderr when running tests added
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.
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.
- Pull request https://github.com/theforeman/foreman-packaging/pull/1436 added
- Pull request https://github.com/theforeman/foreman-packaging/pull/1437 added
- Related to Bug #17871: Circular dependency detected while autoloading constant ConfigReportStatusCalculator added
- Pull request https://github.com/theforeman/foreman-packaging/pull/1493 added
- Pull request https://github.com/theforeman/foreman/pull/4217 added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by