Description of problem: I found a minor typo while translating the UI strings. Version-Release number of selected component (if applicable): 3.6 How reproducible: 100% Actual results: Cannot ${action} ${type}. The VM ${VmName} has sanpshots that must be collapsed. Expected results: Cannot ${action} ${type}. The VM ${VmName} has snapshots that must be collapsed. Additional info: File: AppErrors Resource ID: ACTION_TYPE_FAILED_IMPORT_CLONE_NOT_COLLAPSED
(In reply to Yuko Katabami from comment #0) > Description of problem: > I found a minor typo while translating the UI strings. > > Version-Release number of selected component (if applicable): 3.6 > > > How reproducible: 100% > > > Actual results: > Cannot ${action} ${type}. The VM ${VmName} has sanpshots that must be > collapsed. > > Expected results: > Cannot ${action} ${type}. The VM ${VmName} has snapshots that must be > collapsed. > > Additional info: > > File: AppErrors > Resource ID: ACTION_TYPE_FAILED_IMPORT_CLONE_NOT_COLLAPSED Hi, Can you please provide the steps to reproduce this scenario. Thaks
Unfortunately I do not have steps to reproduce this. It was found during translation in Zanata. Might be involved in VM importing?
Used the following code: ---------------------------------- rhevm-3.6.0-0.18.el6.noarch vdsm-4.17.8-1.el7ev.noarch I tried to reproduce a scenario to generate the string by importing VM's but this string is not displayed. Without specific steps to reproduce this issue I cannot Verify this BZ. Please advise
I can only verify that the strings pushed to zanata is now fixed in both ovirt-3.6 and master versions: Cannot ${action} ${type}. The VM ${VmName} has snapshots that must be collapsed. @Einav, Would this be good enough to move the status VERIFIED?
(In reply to Kevin Alon Goldblatt from comment #3) > Used the following code: > ---------------------------------- > rhevm-3.6.0-0.18.el6.noarch > vdsm-4.17.8-1.el7ev.noarch > > > I tried to reproduce a scenario to generate the string by importing VM's but > this string is not displayed. Without specific steps to reproduce this issue > I cannot Verify this BZ. Please advise This error should occur when you attempt to import a VM that has a snapshot(s), without cloning it, and one or more of the images already exist on the target storage domain.
After the following steps the bug isn't reproduce: 1. create vm with disk 2. create 2 snapshot 3. add 2 additional disks 4. create another snapshot 5. export the vm 6. remove the vm but don't remove the disk attached to him 7. import the vm without cloning it this is the massage received by the engine: Cannot import VM. The Storage Domain already contains the target disk(s). engine-version: 3.6.0.3-0.1.el6 vdsm: 4.17.9-1.el7ev there is no farther steps for us to do.
Since oVirt 3.6.0 has been released, moving from verified to closed current release.