Closed mattiascockburn closed 6 years ago
@mattiasgiese: Thanks, that almost looks like a ready to use bugfix. I'd suggest to rescue the exception like this, though: https://github.com/theforeman/smart_proxy_monitoring/blob/578168a9b29575b797b1ee67350cf6347021b86d/lib/smart_proxy_monitoring_icingadirector/monitoring_icingadirector_main.rb#L22-L23
Do you feel comfortable opening a PR with these changes?
@timogoebel Yup, i'll prepare that in the morning. Cheers!
@timogoebel I guess there is no need for that. It seems you already fixed it in 3792137f88854e84638ae02aab2af21f7e14865d
@mattiasgiese: Perfect, thanks for your time. I just released 0.1.2 that includes the latest fixes.
Heya, experiencing the following with Foreman 1.17.1 and smart_proxy_monitoring-0.1.1: Upon host rebuild, the smart proxy tries to update host attributes in Icinga. If nothing changed between the initial creation of the host and the rebuild icinga-director will return HTTP 304 Not Modified. This leads to an exception in the smart proxy which prevents the rebuild of the host:
The smart proxy will succeed if i change or add any attribute in icinga-director before initiating the rebuild
Hacky workaround which surely introduces other issues: