Description of problem: When updating a virtual machine whose name begins with a numerical value via rhevm-shell, rhevm reports that the virtual machine doesn't exist. Version-Release number of selected component (if applicable): rhevm-cli-3.2.0.9-1.el6ev How reproducible: 100% Steps to Reproduce: 1. create a virtual machine whose name begins with a number. add vm --name '12345' --cluster-name 'SomeCluster' --template-name 'Blank' --os-type rhel_6x64 --type server 2. Attempt to update the virtual machine's description update vm 12345 --description testdescription Actual results: rhevm-shell outputs: error: vm "12345" does not exist. Expected results: rhevm-shell properly updates the virtual machines description. Additional info:
(In reply to Rich Jerrido from comment #0) > Description of problem: > > When updating a virtual machine whose name begins with a numerical value via > rhevm-shell, rhevm reports that the virtual machine doesn't exist. > > Version-Release number of selected component (if applicable): > rhevm-cli-3.2.0.9-1.el6ev > > How reproducible: > 100% > > Steps to Reproduce: > 1. create a virtual machine whose name begins with a number. > > add vm --name '12345' --cluster-name 'SomeCluster' --template-name 'Blank' > --os-type rhel_6x64 --type server i see a rest-api issue when creating vm with name of digits: [RHEVM shell (connected)]# add vm --name 2222 --cluster-name Default --template-name Blank error: status: 500 reason: Internal Server Error detail: HTTP Status 500 [RHEVM shell (connected)]# list vms error: status: 500 reason: Internal Server Error detail: HTTP Status 500 > > 2. Attempt to update the virtual machine's description > > update vm 12345 --description testdescription if it's works on your build, you should be sending name as string as you did during creation - '12345', e.g: update vm '12345' --description testdescription > > > > Actual results: > > rhevm-shell outputs: > > error: vm "12345" does not exist. > > Expected results: > > rhevm-shell properly updates the virtual machines description. > > Additional info:
more than this, i can't remove them from the UI, it's looking fro the SD despite all vms have no disks: 3333: Cannot remove VM: Storage Domain cannot be accessed. -Please check that at least one Host is operational and Data Center state is up. can't recall, does naming vm like this is legal at all?
don't see a reason why not, this should be fixed
we have entities (such as events) in the system with id of type long, since the name of the entity is ambiguous in terms of id/name , one should use the id (UUID) of the vm for identification (when name is digits only) and not the name.