Bug 1830640 - Incorrect disk selection in the custom partitioning spoke
Summary: Incorrect disk selection in the custom partitioning spoke
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Vendula Poncova
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-03 08:15 UTC by Jan Stodola
Modified: 2021-04-15 11:12 UTC (History)
8 users (show)

Fixed In Version: anaconda-33.25.3-1
Clone Of:
Environment:
Last Closed: 2021-04-15 11:12:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.log (21.45 KB, text/plain)
2020-05-03 08:15 UTC, Jan Stodola
no flags Details
storage.log (160.94 KB, text/plain)
2020-05-03 08:16 UTC, Jan Stodola
no flags Details
syslog (605.73 KB, text/plain)
2020-05-03 08:16 UTC, Jan Stodola
no flags Details

Description Jan Stodola 2020-05-03 08:15:11 UTC
Description of problem:
The custom partitioning spoke doesn't work with the disks selected in the storage spoke if the disk selection is changed and the custom partitioning spoke is re-visited.

Version-Release number of selected component (if applicable):
Fedora-Server-netinst-x86_64-Rawhide-20200502.n.0.iso
anaconda-33.12-1.fc33

How reproducible:
Always

Steps to Reproduce:
1. Start graphical installation on a system with 2 or more disks
2. Proceed to the storage spoke
3. Select the first drive (vda) and go to custom partitioning
4. Return back to the storage spoke
5. Select only the second drive (vdb) and go back to custom partitioning
6. Let anaconda create mount points

Actual results:
The custom storage spoke says "0 storage devices selected".
Newly created mount points are on the first disk (vda).

Expected results:
The custom storage spoke says "1 storage device selected".
Newly created mount points are on the second disk (vdb).

Comment 1 Jan Stodola 2020-05-03 08:15:44 UTC
Created attachment 1684389 [details]
anaconda.log

Comment 2 Jan Stodola 2020-05-03 08:16:04 UTC
Created attachment 1684390 [details]
storage.log

Comment 3 Jan Stodola 2020-05-03 08:16:22 UTC
Created attachment 1684391 [details]
syslog

Comment 4 Ben Cotton 2020-08-11 15:21:10 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 5 Vladimír Slávik 2020-09-04 11:38:04 UTC
Closing as a duplicate. See https://bugzilla.redhat.com/show_bug.cgi?id=1868577#c33 . Thank you for the report!

*** This bug has been marked as a duplicate of bug 1868577 ***

Comment 6 Vendula Poncova 2020-09-07 11:01:55 UTC
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/2823


Note You need to log in before you can comment on or make changes to this bug.