Closed jakegroves closed 5 years ago
@jakegroves: Thanks for the report. What Foreman Version are you running?
@timogoebel we are running version 1.19 of foreman Puppetdb version = 5.2.4-1 Puppetdb plugin = 4.0.0-1
@timogoebel this appears to be related to: https://projects.theforeman.org/issues/23536 we have the setting 'unattended: false' in settings.yaml which disables the orchestration of hosts and just acts as a simple node classifier, and it appears that the plugin does not take that into account.
@jakegroves: Ok, that makes a lot of sense. Technically, this plugin does not support unattended: false
. But I'll try to add this if I find a couple of spare minutes.
Do you want to have the functionality, that hosts are deleted in puppetdb when they're removed in Foreman?
@timogoebel I see that is fair. We recently moved from puppet 3.8 and theforeman 1.12 and always had that setting disabled. That behaviour you are suggesting is what we would expect :) Not sure on best approach, or what other plugins have done. But presume they use queue when unattended is true orherwise they just use some request against puppetdb api maybe?
I'll close this issue as Foreman 1.22 does not support unattended = false
anymore afaik.
I get the follwoing produced from app/models/concerns/orchestration/puppetdb.rb when i try to delete a host in foreman.
Any reason why? Or is a known bug? As its affecting my puppetdb integration as of now.