Bug 1369886 - SmartState Analysis failed on the RHEL instances from Azure providers
Summary: SmartState Analysis failed on the RHEL instances from Azure providers
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.7.0
Assignee: Hui Song
QA Contact: Jeff Teehan
URL:
Whiteboard:
Depends On:
Blocks: 1337693 1370482
TreeView+ depends on / blocked
 
Reported: 2016-08-24 15:36 UTC by Hui Song
Modified: 2016-09-06 01:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1370482 (view as bug list)
Environment:
Last Closed: 2016-08-30 12:51:44 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Hui Song 2016-08-24 15:36:51 UTC
Description of problem:

To improve the IO performance during scanning, the disk cache is introduced. It caused some disk related information was missed for filesystem parsing.

Version-Release number of selected component (if applicable):
5.6.1.2.20160810181333_8ba817b

How reproducible:


Steps to Reproduce:
1. Choose the instance with RHEL on it from Azure provider;
2. run SSA
3.

Actual results:

[----] D, [2016-08-22T10:04:27.100805 #53700:5c998c] DEBUG -- : MiqDiskCache.d_read(1097728, 4096)
[----] D, [2016-08-22T10:04:27.100892 #53700:5c998c] DEBUG -- : MiqDiskCache.d_read_cached(2144, 8)
[----] D, [2016-08-22T10:04:27.101032 #53700:5c998c] DEBUG -- : LinuxMount: v.dInfo.hardwareId =
[----] E, [2016-08-22T10:04:27.101205 #53700:5c998c] ERROR -- : Unable to mount filesystem.  Reason:[undefined method `+' for nil:NilClass] for VM []
[----] E, [2016-08-22T10:04:27.101445 #53700:5c998c] ERROR -- : MIQExtract.new /var/www/miq/vmdb/gems/pending/fs/modules/LinuxMount.rb:86:in `block in fs_init'
[----] E, [2016-08-22T10:04:27.101558 #53700:5c998c] ERROR -- : MIQExtract.new /var/www/miq/vmdb/gems/pending/fs/modules/LinuxMount.rb:36:in `each'
[----] E, [2016-08-22T10:04:27.101628 #53700:5c998c] ERROR -- : MIQExtract.new /var/www/miq/vmdb/gems/pending/fs/modules/LinuxMount.rb:36:in `fs_init'
[----] E, [2016-08-22T10:04:27.101692 #53700:5c998c] ERROR -- : MIQExtract.new /var/www/miq/vmdb/gems/pending/fs/MiqFS/MiqFS.rb:41:in `initialize'
[----] E, [2016-08-22T10:04:27.101756 #53700:5c998c] ERROR -- : MIQExtract.new /var/www/miq/vmdb/gems/pending/fs/MiqMountManager.rb:41:in `initialize'
[----] E, [2016-08-22T10:04:27.101820 #53700:5c998c] ERROR -- : MIQExtract.new /var/www/miq/vmdb/gems/pending/fs/MiqMountManager.rb:20:in `new'



Expected results:

SSA complete successfully.


Additional info:

Comment 3 Jeff Teehan 2016-08-29 21:28:08 UTC
I'm looking right at my 5612 appliance and see this.  I'm not sure what the problem is.  It works everytime for me, at least with a proper RHEL image.

Name	RHEL72-Demo
IP Addresses	10.1.0.16, 104.40.16.57
MAC Address	00-0D-3A-32-B8-04
Container	 azure: 2 CPUs, 3584 MB
Platform Tools	N/A
Operating System	 Red Hat Enterprise Linux Server release 7.2 (Maipo)
Architecture	
Advanced Settings	 0
Resources	Available
Management Engine GUID	ff917d0a-649f-11e6-97a4-00155d06ac23
Virtualization Type	
Root Device Type	
Lifecycle
Discovered	 Wed Aug 17 17:28:23 UTC 2016
Last Analyzed	 Wed Aug 24 16:07:35 UTC 2016
Retirement Date	 Never
Group	Tenant My Company access
Relationships
Cloud Provider	 AzureJT
Availability Zone	 AzureJT
Cloud Tenants	 None
Flavor	 Standard_A2
VM Template	 None
Drift History	 2
Analysis History	 12
Service	 None
Stack	 RedHat.RedHatEnterpriseLinux72-20160717102500
Cloud Networks	 1
Cloud Subnets	 1
Network Routers	 0
Security Groups	 1
Floating Ips	 1
Network Ports	 1
Cloud Volumes	 0
VMsafe
Enable	false
Compliance
Status	Never Verified
History	Not Available
Power Management
Power State	 on
Last Boot Time	N/A
State Changed On	Wed Aug 17 17:28:23 UTC 2016
Security
Users	 27
Groups	 50
Key Pairs	N/A
Configuration
Packages	 511
Init Processes	 175
Files	 0
Diagnostics


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