Bug 1897065
| Summary: | VMware VM name containing a slash ("/") marked as a critical concern by a Validation service rule | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Migration Toolkit for Virtualization | Reporter: | Ilanit Stein <istein> | ||||
| Component: | General | Assignee: | Peter McGowan <pmcgowan> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Maayan Hadasi <mguetta> | ||||
| Severity: | medium | Docs Contact: | Avital Pinnick <apinnick> | ||||
| Priority: | high | ||||||
| Version: | 2.0.0 | CC: | fdupont, mguetta, pmcgowan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 2.0.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-06-10 17:11:26 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Ilanit Stein
2020-11-12 08:28:33 UTC
Discussions in progress about the validation service. Will revisit to assign to the right person. Test for this condition added in https://github.com/konveyor/forklift-validation/pull/7 This should be part of build 2.0.0-8 / iib:62459. Created attachment 1773675 [details]
mini-rhel7⁄mguetta
@Fabien, @Peter I am verifying this issue with MTV 2.0.0-17 / iib:66911 and the VM name contains '%2f' instead of '/' character of the original VM name (please see attached image) Is it an expected behavior? @mguetta this is not the expected behavior. From the attached screenshot, I think this BZ can be marked VERIFIED, since the critical concern is present. And I think there are 2 new bugs to open: - The / character is escaped to %2f when displaying the VM name - The new line is escaped in the concern message. It contains "\n" in the original message, so there should be more than one line. Thanks Fabien, Regarding the new bugs: 1. I created this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1953925 2. I am not sure what did you mean by "concern message" - Is it the first line where the VM is marked as Critical? Is this row should contain more than one line? I am asking because the information that shows in the attached image seems to me very clear and I don't see the value of adding one more blank line Thanks again Thanks for the new BZ. The message is clear but the validation returns a multiline string, i.e. with "\n", so the UI should respect them. If we think that the message should be a single line, we need to change it on the validation service side. (In reply to Fabien Dupont from comment #9) > The message is clear but the validation returns a > multiline string, i.e. with "\n", so the UI should respect them. If we think > that the message should be a single line, we need to change it on the > validation service side. Bug 1953938 - [MTV][UI] Missing a new line ('\n') in the VM's concern message in "Select VMs for migration" stage Thanks for the clarification The issue is verified as fixed VMware VM name with '/' is marked as critical concern 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 (MTV 2.0.0 images), 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://access.redhat.com/errata/RHEA-2021:2381 |