Bug 1315408
Summary: | Hyphen in LVM name caused wrong filesystem was used to search system files. | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Hui Song <hsong> |
Component: | SmartState Analysis | Assignee: | Hui Song <hsong> |
Status: | CLOSED ERRATA | QA Contact: | Satyajit Bulage <sbulage> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.5.0 | CC: | dajohnso, hsong, jhardy, jprause, nachandr, obarenbo |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.6.0 | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | smartstate | ||
Fixed In Version: | 5.6.0.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-06-29 15:40:36 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: |
Description
Hui Song
2016-03-07 16:28:49 UTC
Linux OS will automatically double hyphen, if it exists in the LVM name whenever using as device path. Ex. if vgname = rhel_dhcp181-root, lvname = var, the device path will be /dev/mapper/rhel_dhcp181--root-var. Ignorance this may return empty information in smart state scanning. https://github.com/ManageIQ/manageiq/issues/7039 Please add verification steps. (In reply to Satyajit Bulage from comment #3) > Please add verification steps. 1. Create a VM with multiple LVMs. 2. Name LVMs with hyphen inside, such as CFME-root. 3. Install different filesystems in root and other volumes (easier to reproduce the problem). 4. Run SSA to verify the fix. Created lvm's with given information and Successfully ran SmartState Analysis on the VM. SSA did not return an empty information. Verified Version :-5.6.0.7-beta2.6.20160516171555_b1be31f 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 |