Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1680294

Summary: [RFE][machines] Allow Performance options such as directsync, writeback, writethrough to disks in cockpit GUI.
Product: Red Hat Enterprise Linux 8 Reporter: Siddhant Rao <sirao>
Component: cockpit-appstreamAssignee: Martin Pitt <mpitt>
Status: CLOSED ERRATA QA Contact: YunmingYang <yunyang>
Severity: low Docs Contact:
Priority: medium    
Version: 8.0CC: kkoukiou, mtessun, qiyuan, xchen, yunyang
Target Milestone: rcKeywords: Rebase
Target Release: 8.1Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 20:41:39 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Siddhant Rao 2019-02-23 17:38:15 UTC
Description of problem:
Allow Performance options such as directsync, writeback, writethrough to disks in cockpit GUI.

Version-Release number of selected component (if applicable):
cockpit-185-2.el8.x86_64
cockpit-machines-184.1-1.el8.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Such options are not there at present.

Expected results:
Such options have been present earlier in previous GUI based applications such as virt-manager.

Additional info:

Comment 1 Katerina Koukiou 2019-05-24 16:42:45 UTC
commit 8da72535f8937f42702804306b4091ca3f4b036a
Author: Katerina Koukiou <kkoukiou>
Date:   Tue May 21 15:19:56 2019 +0200

    machines: add option to change disk cache mechanism when adding new disks


$ git describe 8da72535f8937f42702804306b4091ca3f4b036a
194-80-g8da72535f

Comment 3 YunmingYang 2019-06-20 03:11:49 UTC
Test Versions:
cockpit-machines-196-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64


Test Steps:
1.Prepare a VM
2.Add disk for the VM with choosing one of the performance options
3.Check it by 'virsh dumpxml ${vm} | grep volume'
4.Repeat the step 2 and 3, in order to choose test all the performance options

Test Results:
1. The disk can be added correctly, and the result by using 'virsh dumpxml ${vm} | grep volume' is the same as the page


According to the results, move the status to VERIFIED.

Comment 5 errata-xmlrpc 2019-11-05 20:41:39 UTC
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-2019:3325