Bug 1817306
| Summary: | Blacklisting is not done for LVM cache fast devices | ||
|---|---|---|---|
| Product: | [oVirt] cockpit-ovirt | Reporter: | SATHEESARAN <sasundar> |
| Component: | gluster-ansible | Assignee: | Parth Dhanjal <dparth> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.14.2 | CC: | bugs, dparth, godas, rhs-bugs |
| Target Milestone: | ovirt-4.4.0 | Flags: | sasundar:
ovirt-4.4?
sasundar: planning_ack? godas: devel_ack+ sasundar: testing_ack+ |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | cockpit-ovirt-0.14.5 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1817305 | Environment: | |
| Last Closed: | 2020-05-20 19:59:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1817305 | ||
|
Description
SATHEESARAN
2020-03-26 04:53:08 UTC
Tested with cockpit-ovirt-dashboard-0.14.5-1.el8ev.noarch with the following steps:
1. Started the RHHI-V deployment from web console
2. Provided the values for hosts, volumes.
3. On the bricks tab, with the default 'blacklist gluster devices' enabled,
also enabled 'lvmcache' SSD device as '/dev/sdg' and provided the details.
The generated inventory file included this LVM device also under blacklist_mpath_devices
[root@ ~]# grep blacklist_mpath /etc/ansible/hc_wizard_inventory.yml -A5
blacklist_mpath_devices:
- sdb
- sdc
- sdd
- sdg
gluster_infra_cache_vars:
--
blacklist_mpath_devices:
- sdb
- sdc
- sdd
- sdg
gluster_infra_cache_vars:
--
blacklist_mpath_devices:
- sdb
- sdc
- sdd
- sdg
gluster_infra_cache_vars:
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |