New commit detected on ManageIQ/manageiq/hammer:
Author: Adam Grare <email@example.com>
AuthorDate: Fri Feb 15 14:14:07 2019 -0500
Commit: Adam Grare <firstname.lastname@example.org>
CommitDate: Fri Feb 15 14:14:07 2019 -0500
Merge pull request #18451 from fdupont-redhat/v2v_escape_unicode_for_wrapper
Escape characters in SSH URI for virt-v2v
(cherry picked from commit b652050c9e9c37e50672978aa0a2f939cc7510a8)
app/models/service_template_transformation_plan_task.rb | 7 +-
spec/models/service_template_transformation_plan_task_spec.rb | 6 +-
2 files changed, 9 insertions(+), 4 deletions(-)
Created attachment 1538366 [details]
For RHV, vm with international characters (ytale-õpêô-aññ-bédévé-日本語-简体中文-жгф-001) migrated but vm with space (ytale space) failed to migrate with 'Update description of VM' status.
Created attachment 1538403 [details]
Could not check this BZ on OSP yet due to some volume issues .
WIll check tomorrow and comment on OSP.
But as @Yadnyawalk mentioned , VM with space in the name failed to migrate on RHV
Moving this BZ to assigned.
Created attachment 1538615 [details]
log for international chars vm with OSP
International chars not fixed for OSP .
Vm with space name gets migrated successfully on OSP .
SO two issues to fix :
Vm with space on RHV and
VM with international chars on OSP.
Appliance : https://10.8.198.160
This bug will also track International chars and space name VM's for OSP and RHV for both VDDK and SSH .
https://github.com/ManageIQ/manageiq-content/pull/509 should fix space issue with RHV.
The solution we agreed is too filter out VMs that have an "invalid" name. By invalid we mean that it's not supported by the destination provider.
https://github.com/ManageIQ/manageiq-content/pull/509 will not solve it, but I'm working on another PR. We may or may not be on time for 5.10.2. If not, I'll move the Target Release to 5.10.3
The invalid VM names will be filtered from the migration plan selection widget with https://bugzilla.redhat.com/show_bug.cgi?id=1685948.
We also document the valid characters set in IMS 1.1 guide.
Let's move this BZ to POST.
New commit detected on ManageIQ/manageiq-content/hammer:
Author: Greg McCullough <email@example.com>
AuthorDate: Thu Mar 7 17:28:03 2019 -0500
Commit: Greg McCullough <firstname.lastname@example.org>
CommitDate: Thu Mar 7 17:28:03 2019 -0500
Merge pull request #509 from fdupont-redhat/v2v_remove_setdescription
[V2V] Remove SetDescription state
(cherry picked from commit 3e726817190816aea92f2357a136d536997ecaeb)
content/automate/ManageIQ/Transformation/Infrastructure/VM/Common.class/__methods__/setdescription.rb | 30 -
content/automate/ManageIQ/Transformation/Infrastructure/VM/Common.class/__methods__/setdescription.yaml | 16 -
content/automate/ManageIQ/Transformation/Infrastructure/VM/rhevm.class/__class__.yaml | 33 -
content/automate/ManageIQ/Transformation/Infrastructure/VM/rhevm.class/__methods__/utils.rb | 67 -
content/automate/ManageIQ/Transformation/Infrastructure/VM/rhevm.class/__methods__/utils.yaml | 13 -
content/automate/ManageIQ/Transformation/Infrastructure/VM/rhevm.class/_missing.yaml | 12 -
content/automate/ManageIQ/Transformation/StateMachines/VMTransformation.class/posttransform.yaml | 16 +-
7 files changed, 4 insertions(+), 183 deletions(-)
Created attachment 1554319 [details]
Migration of VM with international chars in name failed on OSP.
Logs are attached .
Appliance : https://10.8.196.192/
International characters are still not supported for both RHV and OSP, so I don't know why we test them.
Since the BZ came to ON_QA we tested it for space and international chars for which it was reported.
Removing international test case now and validating only for space in VM name.
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.