Project

General

Profile

Bug #31181

Race condition during discovery provisioning

Added by Lukas Zapletal over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Because we cannot use explicit SQL transactions due to #14002 and specifically #14001, concurrent provisioning often run into issues. In this case, max counters are not applied for discovery rules. Rewriting our whole orchestration stack is not going to happen, so I will likely need to implement some "ticketing" system where "reservations" are made in advance (as some kind of counter). Before that, I am starting discussion at:

https://community.theforeman.org/t/orchstration-framework-problems/21020

To at least consider dropping post orchestration queue.

Also available in: Atom PDF