Project

General

Profile

Actions

Feature #5863

closed

dynflow rollback needed when content host creation fails in either candlepin or pulp step

Added by Thomas McKay about 10 years ago. Updated almost 6 years ago.

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

Description

Scenario: Register a content host with an activation key that references a subscription whose quantity is already used. In this case the candlepin dynflow will fail but the katello content host activerecord will exist. The result is an AR w/ uuid=nil and the api/v2/systems will return no results (due to elasticsearch?

Actions

Also available in: Atom PDF