Project

General

Profile

Actions

Feature #15779

closed

Make report, puppet classes and environments importing asynchronous using foreman-tasks

Added by Marek Hulán over 7 years ago. Updated over 5 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.


Related issues 12 (4 open8 closed)

Related to Foreman - Feature #7514: add foreman tasks into coreNewActions
Related to Installer - Feature #17467: Configure tasks by defaultDuplicateIvan Necas11/23/2016Actions
Related to Foreman - Bug #17482: Incorrect concatentation of environment import strings to form sentencesRejectedMarek Hulán11/25/2016Actions
Related to Foreman - Refactor #17483: Async HTTP API calls should return code 202 Accepted instead of 201 CreatedClosedMarek Hulán11/25/2016Actions
Related to Foreman - Bug #17495: Align foreman configuration report expiry with Task expiryClosedMarek Hulán11/27/2016Actions
Related to Foreman - Bug #17575: "Failed importing of report" error printed to stderr when running testsNew12/05/2016Actions
Related to Foreman - Bug #17871: Circular dependency detected while autoloading constant ConfigReportStatusCalculatorNew12/29/2016Actions
Blocked by foreman-tasks - Bug #15778: Can't use process_success Foreman method in API controllers on DynflowTaskClosedMarek Hulán07/22/2016Actions
Blocks foreman-tasks - Refactor #15770: Move reports import and puppet class/environments importing to Foreman coreReady For TestingMarek Hulán07/21/2016Actions
Blocks Hammer CLI - Feature #15780: Support async importing from puppet masterClosedMarek Hulán07/22/2016Actions
Blocked by foreman-tasks - Feature #17283: In thread executor for testing inside transactionsClosedIvan Necas11/09/2016Actions
Blocked by Foreman - Bug #17361: `rake db:drop db:create db:migrate` doesn't migrate pluginsClosedIvan Necas11/16/2016Actions
Actions #1

Updated by Marek Hulán over 7 years ago

  • Blocked by Bug #15778: Can't use process_success Foreman method in API controllers on DynflowTask added
Actions #2

Updated by Marek Hulán over 7 years ago

  • Blocks Refactor #15770: Move reports import and puppet class/environments importing to Foreman core added
Actions #3

Updated by Marek Hulán over 7 years ago

  • Blocks Feature #15780: Support async importing from puppet master added
Actions #4

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3670 added
Actions #5

Updated by Marek Hulán over 7 years ago

Actions #6

Updated by Ivan Necas over 7 years ago

  • Blocked by Feature #17283: In thread executor for testing inside transactions added
Actions #7

Updated by Ivan Necas over 7 years ago

  • Blocked by Bug #17361: `rake db:drop db:create db:migrate` doesn't migrate plugins added
Actions #8

Updated by Ivan Necas over 7 years ago

Actions #9

Updated by Marek Hulán over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #10

Updated by Dominic Cleal over 7 years ago

  • Related to Bug #17482: Incorrect concatentation of environment import strings to form sentences added
Actions #11

Updated by Ewoud Kohl van Wijngaarden over 7 years ago

  • Related to Refactor #17483: Async HTTP API calls should return code 202 Accepted instead of 201 Created added
Actions #12

Updated by Dominic Cleal over 7 years ago

  • translation missing: en.field_release set to 189
Actions #13

Updated by Marek Hulán over 7 years ago

  • Target version set to 1.4.4
Actions #14

Updated by Ohad Levy over 7 years ago

  • Related to Bug #17495: Align foreman configuration report expiry with Task expiry added
Actions #15

Updated by The Foreman Bot over 7 years ago

  • Pull request https://github.com/theforeman/foreman/pull/4075 added
Actions #16

Updated by Dominic Cleal over 7 years ago

  • translation missing: en.field_release changed from 189 to 209

Moving due to continuing build/test failures.

Actions #17

Updated by Dominic Cleal over 7 years ago

  • Related to Bug #17575: "Failed importing of report" error printed to stderr when running tests added
Actions #18

Updated by Marek Hulán over 7 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.

Actions #19

Updated by Dominic Cleal over 7 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.

Actions #20

Updated by The Foreman Bot over 7 years ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/1436 added
Actions #21

Updated by The Foreman Bot over 7 years ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/1437 added
Actions #22

Updated by Ohad Levy about 7 years ago

  • Related to Bug #17871: Circular dependency detected while autoloading constant ConfigReportStatusCalculator added
Actions #23

Updated by The Foreman Bot about 7 years ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/1493 added
Actions #24

Updated by The Foreman Bot about 7 years ago

  • Pull request https://github.com/theforeman/foreman/pull/4217 added
Actions

Also available in: Atom PDF