Bug 1446924

Summary:	different behaviour for Unlock button and Enter when decrypt LUKS
Product:	[Fedora] Fedora	Reporter:	Petr Stodulka <pstodulk>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, mkolman, slukasik, vanmeeuwen+fedora, vponcova
Target Milestone:	---
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:	2017-12-12 10:08:05 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:

Description Petr Stodulka 2017-04-30 14:58:47 UTC

On Fedora 25 there is different behaviour when you want to decrypt a LUKS and you use Unlock button or when you hit Enter on keyboard. The whole process of partitioning when you want to reuse preivously created partitions seems like that:

1) select disk + custom partitioning
2) rescan disk (automatically go back to disk selection...)
3) go again to partitioning
   - now you see unkown parititons
4) unlock luks partition
5) rescan disk again (again you are switched to disk selection ....)
6) and again, go back to partitioning
7) finally, set partitions as you wish

In case you do not click on "Unlock" button but hit enter (when you put password into the intput array in step 4) you can skip steps 5 nad 6 because the rescan of the disk will be done automatically and data about LVM partitions will be updated.

Expected behaviour:
When you click on the Unlock button, anaconda automatically rescan disk and update data without moving back to "disk selection" screen.

Additional info:
As I mentioned here [0], the process is really unfriendly from my point of view, so if there is not any specific reason why there is move back to disk selection screen, I suggest to modify rescan behaviour too, so the whole process could be shorter and more intuitive.

On F26 is anaconda broken [1].

[0] https://bugzilla.redhat.com/show_bug.cgi?id=1348688#c34
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1348688#c33

Comment 1 Šimon Lukašík 2017-05-02 08:33:21 UTC

Nice and thorough description! At least I know what to expect! Many thanks!

Comment 2 Fedora End Of Life 2017-11-16 19:35:24 UTC

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2017-12-12 10:08:05 UTC

Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.