Bug 1533843 - Smart State Analysis for VMware failing with UTF-8 exception on French localized windows VMs.
Summary: Smart State Analysis for VMware failing with UTF-8 exception on French locali...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.8.0
Hardware: All
OS: All
medium
medium
Target Milestone: GA
: 5.10.0
Assignee: Hui Song
QA Contact: Satyajit Bulage
URL:
Whiteboard:
Depends On:
Blocks: 1554343 1554344
TreeView+ depends on / blocked
 
Reported: 2018-01-12 11:02 UTC by Neha Chugh
Modified: 2021-06-10 14:10 UTC (History)
9 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1554343 1554344 (view as bug list)
Environment:
Last Closed: 2018-07-30 14:43:49 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Neha Chugh 2018-01-12 11:02:42 UTC
Description of problem:
Smart State Analysis for VMware failing with UTF-8 exception on French localized windows VMs.

Version-Release number of selected component (if applicable):
Cloudforms 4.5

Steps to Reproduce:
Smart state Analysis is failing with  following error:

[----] I, [2018-01-11T16:07:34.650174 #23412:afd138]  INFO -- : Registry hive [\SystemRoot\System32\Config\SAM] successfully opened for reading in [0.007329826] seconds.  Size:[262144]  Last registry update: [2018-01-11 14:38:35 UTC]
[----] I, [2018-01-11T16:07:34.672142 #23412:afd138]  INFO -- : Registry Parsing time = 0.02188115 sec.  registry segments loaded:[10]
log writing failed. "\xE9" from ASCII-8BIT to UTF-8


Expected results:

Smart state Analysis should performed successfully.


Additional info:
 [yank] complete - access files in /cases/01997851
 [browse] the files here: http://collab-shell.usersys.redhat.com/01997851/

and look at evm.log under 01997851-evm_server.zip

Comment 2 Rich Oliveri 2018-02-01 19:21:32 UTC
That log snippet doesn't show an error, those are informational log messages.

Did the SSA task actually fail - with an error listed in the task display?
Was any data actually collected by the SSA process?

Comment 3 Neha Chugh 2018-02-16 09:11:08 UTC
Hello Rich,

Customer has shared the logs under dropbox with the filename "01997851-evm_server.zip"

Also latest logs are attached to case with the below names:

evm_current_dune131_20180215_234601.tar.xz 
evm_archive_dune131_20180215_233108.tar.xz


And below exceptions are observed in the logs:

[root@dune131 log]*# cat evm.log | grep UTF-8*

[----] E, [2018-02-15T17:02:48.735507 #25262:b7d130] ERROR -- :
MIQ(ManageIQ::Providers::Vmware::InfraManager::Vm#scan_via_miq_vm)
ScanMetadata error status:[8]:  message:[invalid byte sequence in UTF-8]
log writing failed. "\xE9" from ASCII-8BIT to UTF-8
[----] E, [2018-02-15T17:03:31.712051 #25256:b7d130] ERROR -- :
MIQ(ManageIQ::Providers::Vmware::InfraManager::Vm#scan_via_miq_vm)
ScanMetadata error status:[8]:  message:[invalid byte sequence in UTF-8]
log writing failed. "\xE9" from ASCII-8BIT to UTF-8
[----] E, [2018-02-15T17:05:41.879011 #25256:b7d130] ERROR -- :
MIQ(ManageIQ::Providers::Vmware::InfraManager::Vm#scan_via_miq_vm)
ScanMetadata error status:[8]:  message:[invalid byte sequence in UTF-8]
log writing failed. "\xE9" from ASCII-8BIT to UTF-8
[----] E, [2018-02-15T17:06:25.065639 #25262:b7d130] ERROR -- :
MIQ(ManageIQ::Providers::Vmware::InfraManager::Vm#scan_via_miq_vm)
ScanMetadata error status:[8]:  message:[invalid byte sequence in UTF-8]
log writing failed. "\xE9" from ASCII-8BIT to UTF-8
[----] E, [2018-02-15T22:49:41.714034 #8664:b7d130] ERROR -- :
MIQ(ManageIQ::Providers::Vmware::InfraManager::Vm#scan_via_miq_vm)
ScanMetadata error status:[8]:  message:[invalid byte sequence in UTF-8]
log writing failed. "\xE9" from ASCII-8BIT to UTF-8
[----] E, [2018-02-15T22:53:36.949130 #8664:b7d130] ERROR -- :
MIQ(ManageIQ::Providers::Vmware::InfraManager::Vm#scan_via_miq_vm)
ScanMetadata error status:[8]:  message:[invalid byte sequence in UTF-8]
[root@dune131 log]#


Can you help us in understand the root cause behind this exception.

You can access all the logs via collab-shell i.e.

[yank] complete - access files in /cases/01997851


Let me know if you need any further information regarding the same.

Regards,
Neha Chugh

Comment 14 Joachim Boyer 2018-03-08 14:04:41 UTC
From the customer, from the case:
here is the detail ,

*1. Create / Install Windows Server 2012 VM on vSphere 6  *
No ,  *vSphere 5.5  *


*2. French language pack installed. *
No,  The OS is already in French no language pack installed ,
SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_French_-2_Core_MLF_X19-31420


*3. Configure the appliance for SSA.*
No

*4. Version of the device used: 5.8.2.3.20171016155816_aaec796 *

Yes , Version 5.8.2.3.20171016155816_aaec796


An installation with a language pack is different
Have you done the test with registry entries containing French type
accented characters?

Comment 19 CFME Bot 2018-03-09 16:42:13 UTC
New commit detected on ManageIQ/manageiq-gems-pending/master:

https://github.com/ManageIQ/manageiq-gems-pending/commit/5aa3f3d0ffb6c9842d5f51ac52bc9c9d453d93fd
commit 5aa3f3d0ffb6c9842d5f51ac52bc9c9d453d93fd
Author:     hsong-rh <hsong>
AuthorDate: Fri Mar  9 10:08:04 2018 -0500
Commit:     hsong-rh <hsong>
CommitDate: Fri Mar  9 10:08:04 2018 -0500

    Fixed to validate attributes before inserting into XML.

    https://bugzilla.redhat.com/show_bug.cgi?id=1533843

 lib/gems/pending/util/xml/miq_rexml.rb | 3 +-
 1 file changed, 2 insertions(+), 1 deletion(-)

Comment 23 Dave Johnson 2018-07-30 14:43:49 UTC
Closing this as its already been verified in two z-streams and has test coverage around it.


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