Bug 1807815 - [RFE]Provide option to control blacklist or whitelist multipath devices from cockpit
Summary: [RFE]Provide option to control blacklist or whitelist multipath devices from ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: gluster-ansible
Version: ---
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.4.0
: 0.14.3
Assignee: Parth Dhanjal
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1807808 1807814
TreeView+ depends on / blocked
 
Reported: 2020-02-27 10:07 UTC by Gobinda Das
Modified: 2020-07-13 09:28 UTC (History)
5 users (show)

Fixed In Version: cockpit-ovirt-0.14.3
Clone Of: 1807808
Environment:
Last Closed: 2020-05-20 20:03:31 UTC
oVirt Team: Gluster
Embargoed:
sbonazzo: ovirt-4.4?
sbonazzo: planning_ack?
godas: devel_ack+
sasundar: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 107220 0 master MERGED Include multipath checkbox on bricks tab 2020-08-31 06:50:30 UTC

Description Gobinda Das 2020-02-27 10:07:52 UTC 
Description of problem:
  From cockpit based deployment now we don't have any option to blacklist multipath device, user has to manually blacklist. From cockpit UI user should choose whether to disable or enable mutipath devices.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 SATHEESARAN 2020-03-30 05:20:55 UTC 

Tested with cockpit-ovirt-dashboard-0.14.3 with the following steps:

1. Start the HC deployment from cockpit
2. Populate the 'hosts' tab with Storage network FQDN & Public network FQDN
3. Proceed to next tab, fill the volume details
4. Check the bricks tab

Observation:
1. Bricks tab has an option to blacklist the gluster device, which by 
default is enabled.
Comment 2 Sandro Bonazzola 2020-05-20 20:03:31 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.