Closed pfried closed 7 years ago
Your problem sits in your IDO database. Please note that even when storing UTF8 data, the only safe way of creating/using the schema for a long time used to be latin1. Please do not ask why, i tried hard to change this - but failed for non-technical reasons. We'll get this right in IcingaDB, the upcoming IDO successor - but for now we're stick with what we have. Please search the icingaweb2 issue tracker for related issues, and configure your IDO DB resource in Icinga Web 2 being latin1.
Director bases itself on the monitoring module in this particular place, it doesn't run the queries by itself. For the 1.4 (next) branch I'll add a try/catch block silently discarding this error.
Pushed to next
, will be part of 1.4.0. Still, you have to solve your problem elsewhere. Director will no longer fail here, but it cannot fix your problem.
I copy&pasted a hostname in hosts in the director. The name appeared to be UTF-8. Unfortunately now I cannot edit the item anymore as i get an error. I also tried to delete the object via cli which does not work either
Expected Behavior
One should be able to at least delete broken items. I had a similar case before where i had items broken and was not able to delete them via web or cli. This is annoying as you have broken objects in director which propably even lead to broken configuration which cannot be deployed then.
Current Behavior
Director accepts other charsets but cannot handle them afterwards
Error shown is
Possible Solution
Validate input in the input fields.
Or which I think would be nice: Be able to delete items from the list view.
Steps to Reproduce (for bugs)
Context
I am setting up a new environment
Your Environment
icinga2 --version
): r2.6.3-1)