Project

General

Profile

Actions

Bug #7362

closed

Org create dynflow needs to follow the org destroy formula

Added by Partha Aji almost 10 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Orchestration
Target version:
Difficulty:
medium
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Org create dynflow currently uses sync actions in the model. This means the dynflow orchestration is called as an after_create. This creates validation issues for bugs relating to create vs update, i.e http://projects.theforeman.org/issues/6946 . Here for example the after_create mode of the org is set to update, which causes the save inside orchestration layer to get confused.

Also in the long term we want a consistent approach for org creation , where the create call actually calls the dynflow action which handles all the orchestration aspects of the org including AR/Candllepin/Pulp/Foreman layers..

Actions #1

Updated by The Foreman Bot almost 10 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/4642 added
  • Pull request deleted ()
Actions #2

Updated by Eric Helms almost 10 years ago

  • Triaged changed from No to Yes
Actions #3

Updated by Eric Helms almost 10 years ago

  • Target version changed from 55 to 56
Actions #4

Updated by Partha Aji almost 10 years ago

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

Updated by Eric Helms over 9 years ago

  • Translation missing: en.field_release set to 14
Actions

Also available in: Atom PDF