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 Analysis | Assignee: | Hui Song <hsong> | |
Status: | CLOSED ERRATA | QA Contact: | Niyaz Akhtar Ansari <nansari> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 5.5.0 | CC: | carnott, cpelland, dajohnso, hsong, jhardy, jocarter, jprause, mfeifer, nansari, obarenbo, pmcgowan, psavage, roliveri | |
Target Milestone: | GA | Keywords: | 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
Assigning to add test case *** Bug 1297022 has been marked as a duplicate of this bug. *** Hi Hui, Please add verification steps. Thanks 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 Hi Colin, Can you please provide more details around the automated install configuration like the kickstart file itself? Thanks 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 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 |