*** Bug 1325723 has been marked as a duplicate of this bug. ***
Works for me on these components: Engine: rhevm-3.6.5.1-0.1.el6.noarch Linux 2.6.32-573.8.1.el6.x86_64 #1 SMP Fri Sep 25 19:24:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 6.7 (Santiago) Host: ovirt-vmconsole-1.0.0-1.el7ev.noarch mom-0.5.2-1.el7ev.noarch qemu-kvm-rhev-2.3.0-31.el7_2.11.x86_64 sanlock-3.2.4-2.el7_2.x86_64 libvirt-client-1.2.17-13.el7_2.4.x86_64 ovirt-vmconsole-host-1.0.0-1.el7ev.noarch vdsm-4.17.23-0.el7ev.noarch Linux 3.10.0-327.el7.x86_64 #1 SMP Thu Oct 29 17:29:29 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 7.2 (Maipo) I've created the VM named "ожидаемые" with disk named "ожидаемые", also gave comments and description to the VM as "ожидаемые". The VM started normally without any issues. I've also tried to use Hebrew naming and named another VM "שמוליק" with description and comment named with the same name, the VM started OK, the disk was named "שמוליק" too.
All patches are VDSM, not ovirt-engine, fixing component. External trackers must match product/component
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0660.html