Closed mleklund closed 5 years ago
@mleklund: Thanks for the report. Does this actually break any functionality for you? I want to be totally honest with you here: This error occurs because the rendering engine in Foreman core is very messed up. I started to work on this in a Redmine issue but haven't finished the work. I guess you can imagine, that this isn't a trivial task.
It is on the reboot popup (and in the logs) when I "build", but does not seem to do anything other then alert you there is a problem or at least a potential one. Since is does not effect functionality, maybe an update to the readme would be merited?
I think this plugin is amazing for those of us who want to use coreos, but were struggling with how to not move off of foreman with the introduction of ignition and deprecation of cloud_config. I only want to help make it as quality a plugin as possible, so it gains acceptance and long term support. (I have lost foreman-memcache, foreman-columnview, and foreman-host-rundeck over the last couple of releases)
@mleklund: Thanks for the feedback. It is greatly appreciated. We do use this plugin in production so I don't expect it to die soon. I've also taken ownership of foreman_memcache. I'll see to it that it at least keeps working. I'll also update the README.
Feel free to raise feature requests as issues here.
On the upside I have not noticed foreman-memcache missing. So the work to make foreman faster has definitely made a difference.
This should be fixed with Foreman 1.20 so I'll go ahead and close this issue.
Foreman 1.17, foreman_omaha 1.0 + changes from master
Willing to help debug if needed.