Bug 2185235
| Summary: | [RFE] [Machines] ability to refresh storage pool volumes in the cockpit | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Marian Jankular <mjankula> |
| Component: | cockpit-appstream | Assignee: | Simon Kobyda <skobyda> |
| Status: | CLOSED MIGRATED | QA Contact: | YunmingYang <yunyang> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8.7 | CC: | sbarcomb |
| Target Milestone: | rc | Keywords: | FutureFeature, MigratedToJIRA |
| Target Release: | 8.9 | Flags: | pm-rhel:
mirror+
|
| 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: | 2023-09-15 13:57:18 UTC | Type: | Story |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marian Jankular
2023-04-07 13:36:07 UTC
Hey, so to understand this better, I have 2 question: 1. How do you add a new volume to your storage pool? We refresh pool automatically when new volume is created. Do you use some other tool for adding volume to pool? Or (in case it's file-based storage pool) do you just move a file into a directory of the pool? 2. What do you use that volume for? If you immediately use that volume as a disk for a VM in "Add disk" dialog, or as a storage in "Create VM" dialog, maybe it could be better if Cokpit automatically refreshed a list of volumes every time "Create VM" dialog or "Add disk" dialogs are opened. Would that solve your problem? Q1: 1. How do you add a new volume to your storage pool? We refresh the pool automatically when a new volume is created. Do you use some other tool for adding volume to the pool? Or (in case it's a file-based storage pool) do you just move a file into a directory of the pool? A1: i was able to reproduce it with a file-based local storage pool when I created a disk with qemu-img create ...., and when I logged to the cockpit and I did not see the image, it was displayed immediately when I issued "virsh pool-refresh --pool <POOL>" or disabled and enabled the pool in the cockpit. Q2. What do you use that volume for? If you immediately use that volume as a disk for a VM in "Add disk" dialog, or as a storage in "Create VM" dialog, maybe it could be better if Cockpit automatically refreshed a list of volumes every time "Create VM" dialog or "Add disk" dialogs are opened. Would that solve your problem? A2: so far everytime i creaded disk in the cockpit it was visible in cockpit, so i would say if there would be button to refresh it manually it would be the best as somebody could crewate it in terminal as me and customer did. (In reply to Marian Jankular from comment #3) > A2: so far everytime i creaded disk in the cockpit it was visible in > cockpit, so i would say if there would be button to refresh it manually it > would be the best as somebody could crewate it in terminal as me and > customer did. But user refreshes the storage pool volumes so they have up-to-date list of volumes available for some subsequent action. The user doesn't want to go to cockpit to ONLY refresh the pool. Your user would go to cockpit, refresh the pool's volume list, and then use the refreshed volumes for some desired action (e.g. attaching it as a disk to a VM, or deleting the storage volume), right? And the pool refresh is just an intermediate step, right? So instead, wouldn't it be better for the user to not have to click on "Refresh", to not have to do the refresh manually. But instead, they would have automatically refreshed, up-to-date list of volume available when they want to do the desired action with the volumes (e.g. attaching it as a disk to a VM)? The point is, I still don't see the use case of just having standalone "Refresh" button somewhere. From what I know, the pool refresh is always just an intermediate action, which we can always do automatically as a prerequisite of some other action. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |