Problem:
Try to delete host that got had NetworkMangler hosed up and keep getting
Executing dynflow action inside a transaction is not a good idea
Expected outcome:
Host deleted
Foreman and Proxy versions:
1.16.2
Foreman and Proxy plugin versions:
Other relevant data:
There are no jobs in Dynaflow that aren’t successful, stopped, Actions::Candlepin::ListenOnCandlepinEvents and Actions::Katello::EventQueue::Monitor.
Do you happen to have the foreman-chef plugin installed?
That did it.
Part of my testing for a POC is to also test Chef. What is the fix here to get this so it works properly with Chef installed?
Is there a fix out there yet to allow Chef to work properly without causing Dynaflow to kick out this message? Maybe there is a re-declaration of a function with the same name so the two are conflicting?
I’m not a Ruby coder, though I have hacked a few scripts, so I’m not even sure where to start digging to try to find where this problem exists.
Has it been fixed in the 17.x and 18.x versions of Foreman?
As an add-on here, the subscription-manager registration in a kickstart or finish template still fails on the dynaflow error.