Bug 1276906

Verified using vt18

- VM can not be created if Russian characters are used in Disk Alias Field.
Works fine
- VM can not not be started if Russian characters are used in VM Name Field.
Still can't start the VM

from engine log - 
=================
2015-11-04 18:28:19,678 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-57) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM Опишите is down with error. Exit message: 'ascii' codec can't decode byte 0xd0 in position 68: ordinal not in range(128).
2015-11-04 18:28:19,678 INFO  [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-57) Running on vds during rerun failed vm: null
2015-11-04 18:28:19,680 INFO  [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-57) VM Опишите (90be29a9-b274-46f5-a439-6ae5a1ca33c9) is running in db and not running in VDS camel-vdsb
2015-11-04 18:28:19,971 ERROR [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-57) Rerun vm 90be29a9-b274-46f5-a439-6ae5a1ca33c9. Called from vds camel-vdsb
2015-11-04 18:28:20,093 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-7-thread-15) Correlation ID: 2965ccf4, Job ID: 290527ca-0caa-44c8-a460-b0713d114699, Call Stack: null, Custom Event ID: -1, Message: Failed to run VM Опишите on Host camel-vdsb.
2015-11-04 18:28:20,109 INFO  [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-7-thread-15) Lock Acquired to object EngineLock [exclusiveLocks= key: 90be29a9-b274-46f5-a439-6ae5a1ca33c9 value: VM
, sharedLocks= ]
2015-11-04 18:28:20,144 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (org.ovirt.thread.pool-7-thread-15) START, IsVmDuringInitiatingVDSCommand( vmId = 90be29a9-b274-46f5-a439-6ae5a1ca33c9), log id: 18f15bcf
2015-11-04 18:28:20,160 INFO  [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (org.ovirt.thread.pool-7-thread-15) FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 18f15bcf
2015-11-04 18:28:20,178 WARN  [org.ovirt.engine.core.bll.RunVmCommand] (org.ovirt.thread.pool-7-thread-15) CanDoAction of action RunVm failed for user admin@internal. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_NO_HOSTS



I am not sure I understand, do we support or should block ? anyway we are not blocking nor supporting...

Wrote by mistake verified in comment #1

if this isn't a blocker and still open please move to 3.5.7.

since the storage part is fixed and only the virt part of the VM name and starting the VM is left I'm moving to virt (see also Bug #1260131)

As for VM name:
- VDSM crashes in logging code (I'll fix it).
- libvirt fails to create domain with non-ASCII characters in its name, see https://bugzilla.redhat.com/show_bug.cgi?id=1062943

according to https://bugzilla.redhat.com/show_bug.cgi?id=1191835#c1 it seems to be broken since Fedora 20, so I guess all RHEL 7 hypervisors are affected

unlikely to be fixed within 3.5.z timeframe, I propose closing wontfix

(In reply to Michal Skrivanek from comment #8)
> unlikely to be fixed within 3.5.z timeframe, I propose closing wontfix

closing this one since it introduces a risk for zstream due to the change needed. 
this bug is being addressed on 3.6 release.