Bug 2263972
| Summary: | Cockpit storage: incorrectly displays the "Type" of an EFI system partition it previously created as "vfat filesystem" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||
| Component: | cockpit | Assignee: | Marius Vollmer <mvollmer> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | kkoukiou, mmarusak, mpitt, patrick, stefw | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | cockpit-311-1.fc39 cockpit-311-1.fc38 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2024-02-16 01:41:14 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2231339 | ||||||
| Attachments: |
|
||||||
|
Description
Adam Williamson
2024-02-13 02:40:27 UTC
Created attachment 2016556 [details]
screenshot of the issue (affected partition is vda1)
"Technically", Cockpit is not wrong: the EFI system partition indeed has a vfat filesystem on it, and the thing that makes it EFI is its partition type. But I agree that this is not helpful and Cockpit should list the EFI system partition as "EFI System partition". Cockpit might even start complaining if you a partition has the EFI type but not a vfat filesystem, or a different mount point than /boot/efi. This is even worse for bios boot partitions: they don't even have a filesystem on them and are listed as "Unformatted data". Thanks for pointing this out! I have bumped the priority for fixing this. FEDORA-2024-7b0bc52005 (cockpit-311-1.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-7b0bc52005 FEDORA-2024-be44af3059 (cockpit-311-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-be44af3059 FEDORA-2024-be44af3059 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-be44af3059` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-be44af3059 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-7b0bc52005 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-7b0bc52005` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-7b0bc52005 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-be44af3059 (cockpit-311-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-7b0bc52005 (cockpit-311-1.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. |