Bug 1302851

Summary: smart state error "Unable to mount filesystem. Reason:[No root filesystem found.]"
Product: Red Hat CloudForms Management Engine Reporter: Josh Carter <jocarter>
Component: SmartState AnalysisAssignee: Hui Song <hsong>
Status: CLOSED ERRATA QA Contact: Niyaz Akhtar Ansari <nansari>
Severity: high Docs Contact:
Priority: high    
Version: 5.5.0CC: carnott, cpelland, dajohnso, hsong, jhardy, jocarter, jprause, mfeifer, nansari, obarenbo, pmcgowan, psavage, roliveri
Target Milestone: GAKeywords: ZStream
Target Release: 5.6.0   
Hardware: All   
OS: All   
Whiteboard: vsphere:vm:smartstate
Fixed In Version: 5.6.0.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1306416 1430356 (view as bug list) Environment:
Last Closed: 2016-06-29 15:34:49 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:
Bug Depends On:    
Bug Blocks: 1306416, 1430356    

Description Josh Carter 2016-01-28 19:05:26 UTC
Description of problem:

VCenter 6.0
vix vddk 6.0.1

The appliance is able to smart state itself which also resides on the same vcenter as the other guest that are unable to be scanned. 

The guest systems that raise the "No root filesystem found" are Rhel 7 guest 
with EXT4 filesytem that is spread across 3 disk. Normally / is on one disk, /swap is on a second and then user directories is on a third.

[----] I, [2016-01-22T14:57:06.661604 #3031:ff5988]  INFO -- : Q-task_id([3578e126-c142-11e5-b7be-005056a6315c]) MIQ(MiqQueue.put) Message id: [404000000281776],  id: [], Zone: [
default], Role: [automate], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [MiqAeEngine.deliver], Timeout: [3600], Priority: [20], State: [re
ady], Deliver On: [], Data: [], Args: [{:object_type=>"ManageIQ::Providers::Vmware::InfraManager::Vm", :object_id=>404000000000505, :attrs=>{:event_type=>"vm_scan_abort", "VmOrTe
mplate::vm"=>404000000000505, :vm_id=>404000000000505, "Host::host"=>404000000000001, :host_id=>404000000000001, "MiqEvent::miq_event"=>404000000005880, :miq_event_id=>404000000005880, "EventStream::event_stream"=>404000000005880, :event_stream_id=>404000000005880}, :instance_name=>"Event", :user_id=>404000000000002, :miq_group_id=>404000000000017, :tenant_id=>404000000000001, :automate_message=>nil}]
[----] E, [2016-01-22T14:57:06.661711 #3031:ff5988] ERROR -- : Q-task_id([3578e126-c142-11e5-b7be-005056a6315c]) MIQ(VmScan#process_abort) job aborting, Unable to mount filesystem.  Reason:[No root filesystem found.]
[----] I, [2016-01-22T14:57:06.678714 #3031:ff5988]  INFO -- : Q-task_id([3578e126-c142-11e5-b7be-005056a6315c]) MIQ(VmScan#process_finished) job finished, Unable to mount filesystem.  Reason:[No root filesystem found.]


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Shveta 2016-02-01 21:32:52 UTC
Assigning to add test case

Comment 26 Rich Oliveri 2016-03-02 16:59:38 UTC
*** Bug 1297022 has been marked as a duplicate of this bug. ***

Comment 39 Niyaz Akhtar Ansari 2016-05-04 10:27:40 UTC
Hi Hui,

Please add verification steps.

Thanks

Comment 40 Hui Song 2016-05-04 13:07:04 UTC
This issue only happens when the root filesystem is ext4 and group descriptor size is 64:

1. Use RHEL-Server automated installer (Comment 21) to create a VM. The created VM should meet the above conditions.
2. Use command mount to verify the root filesystem is ext4.
3. Use command dumpe2fs to verify the group descriptor size (Comment 20).
4. Verify the fix

Comment 41 Niyaz Akhtar Ansari 2016-05-25 18:18:54 UTC
Hi Colin,

Can you please provide more details around the automated install configuration like the kickstart file itself? 

Thanks

Comment 44 Niyaz Akhtar Ansari 2016-06-20 08:59:43 UTC
Created a VM with root filesystem ext4 and group descriptor size 64,
SmartState Analysis  Works Successfully. 

Verified in 5.6.0.11-rc2.2.20160614152915_f315c68

Comment 46 errata-xmlrpc 2016-06-29 15:34:49 UTC
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.

https://access.redhat.com/errata/RHBA-2016:1348