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 1590646

Summary: [RFE] The logical volumes detail should be expanded automatically when clicking on the special filesystem item.
Product: Red Hat Enterprise Linux 7 Reporter: Wei Wang <weiwang>
Component: cockpitAssignee: Marius Vollmer <mvollmer>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: low    
Version: 7.5CC: bugs, cshao, huzhao, qiyuan, weiwang, yaniwang, ycui
Target Milestone: pre-dev-freezeKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-15 07:39:28 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:
Attachments:
Description Flags
picture-fs_1.png
none
picture-fs_2.png none

Description Wei Wang 2018-06-13 06:21:11 UTC
Created attachment 1450795 [details]
picture-fs_1.png

Description of problem:
Suggest making the logical volumes detail expanding automatically when clicking on the special filesystem item on storage page. Now when clicking any filesystem item, the same page will be displayed. The user needs to re-select what logical volumes they want to handle.


Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.2-20180608.1
cockpit-system-165-3.el7.noarch
cockpit-bridge-165-3.el7.x86_64
cockpit-storaged-165-3.el7.noarch
cockpit-165-3.el7.x86_64
cockpit-machines-ovirt-165-3.el7.noarch
cockpit-ovirt-dashboard-0.11.28-1.el7ev.noarch
cockpit-ws-165-3.el7.x86_64
cockpit-dashboard-165-3.el7.x86_64
imgbased-1.0.18-0.1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Clean install redhat-virtualization-host-4.2-20180608.1
2. Login to cockpit WebUI with the root account
3. Go to storage page, click any item in Filesystems list (fs_1.png).


Actual results:
Enter the same page, cannot enter into the special logical volume detail table, need to re-select volumes.


Expected results:
The logical volumes detail expands automatically when clicking on the special item in Filesystem list. (fs_2.png)


Additional info:

Comment 1 Wei Wang 2018-06-13 06:22:01 UTC
Created attachment 1450796 [details]
picture-fs_2.png

Comment 5 RHEL Program Management 2021-02-15 07:39:28 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.