Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1832822

Summary: Cockpit: Blacklist list in inventory file entering empty fields
Product: [oVirt] cockpit-ovirt Reporter: Parth Dhanjal <dparth>
Component: gluster-ansibleAssignee: Parth Dhanjal <dparth>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.14.5CC: bugs, godas
Target Milestone: ovirt-4.4.1Flags: sasundar: ovirt-4.4?
godas: devel_ack+
Target Release: 0.14.8   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.14.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1832879 (view as bug list) Environment:
Last Closed: 2020-08-05 06:24:39 UTC Type: Bug
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: 1832879    

Description Parth Dhanjal 2020-05-07 10:31:39 UTC
Description of problem:
Blacklist device list includes lvcache device even when lvcache isn't enabled.


Version-Release number of selected component (if applicable): cockpit-ovirt-0.14.6


How reproducible: Always


Steps to Reproduce:
1. Generate inventory file through cockpit-ovirt without enabling lvcache

Actual results:

```
      blacklist_mpath_devices:
        - sdb
        - ''
```

Expected results:

```
      blacklist_mpath_devices:
        - sdb
```

Additional info:

Comment 1 Sandro Bonazzola 2020-05-18 14:46:33 UTC
Moved to 4.4.1 not being marked as blocker for 4.4.0 and we are preparing to GA.

Comment 2 SATHEESARAN 2020-07-14 06:01:23 UTC
Verified with cockpit-ovirt-dashboard-0.14.9

When providing the default values for bricks, there is no empty fields generated for blacklist task

Comment 3 Sandro Bonazzola 2020-08-05 06:24:39 UTC
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.1 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.