Bug 1382265 - Issue with "_x" in VM name on SCVMM
Summary: Issue with "_x" in VM name on SCVMM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Documentation
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: Red Hat CloudForms Documentation
QA Contact: Red Hat CloudForms Documentation
URL:
Whiteboard: scvmm:vm
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 07:30 UTC by Leo Khomenko
Modified: 2019-12-19 15:46 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-19 15:46:26 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
lkhomenk: automate_bug-


Attachments (Terms of Use)
screen from CFME vs RDP(scvmm) (177.20 KB, image/png)
2016-10-06 07:30 UTC, Leo Khomenko
no flags Details

Description Leo Khomenko 2016-10-06 07:30:19 UTC
Created attachment 1207834 [details]
screen from CFME vs RDP(scvmm)

Description of problem:if  VM name contains "_x" it will be shown as "_x005F_x"


Version-Release number of selected component (if applicable):5.6.2.1 / 5.7.0.3


How reproducible:100%


Steps to Reproduce:
1.Provision VM with "test_x" name on SCVMM
2.Request will stuck on Verifying New VM
3.

Actual results:VM is getting provisioned , but with "test_x005Fx" name, but on provider's UI VM name is correct - test_x (you can also just rename existing VM on SCVMM to have "_x")


Expected results:"test_x" vm in CFME


Additional info:this affects only SCVMM, other infra/cloud providers are fine

Comment 3 Daniel Berger 2016-10-25 19:12:55 UTC
This is the result of some peculiar behavior with the Export-Clixml command where it automatically converts "_x" to "_x005F_x". I suspect this is ultimately an artifact of xquery behavior.

Comment 4 Bronagh Sorota 2016-10-26 14:48:36 UTC
The described bug occurs when a VM name contains the characters "_x", for example "test_x". The Powershell cmdlet that exports the inventory hash to XML (Export-CLIXML) escapes _x  to _x005F_x. This is something we cannot prevent from happening and I see no way to address it in CF in a scalable way. 
I think it would be helpful to create a KB article on this.

Comment 5 Dave Johnson 2016-10-26 16:31:52 UTC
Re-opening for a documentation note if that makes sense.

Comment 6 Bronagh Sorota 2016-10-26 16:33:43 UTC
Thanks Dave, makes sense to me.


Note You need to log in before you can comment on or make changes to this bug.