| Summary: | " Encryption Options" seems doesn't work well | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | lnie <lnie> | ||||
| Component: | cockpit | Assignee: | Dominik Perpeet <dperpeet> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 25 | CC: | dperpeet, ichavero, stefw | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | cockpit-125-1.fc25 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-12-15 09:10:35 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: | |||||
| Attachments: |
|
||||||
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. See https://github.com/cockpit-project/cockpit/pull/5343 The fundamental issue was a misunderstanding of the UDisks2 API on my part. When there is a stored passphrase, it will always be used, and Cockpit shouldn't open a dialog to ask for one. We can improve this further, of course, and help the user fix a wrong stored passphrase. I don't think we should allow the user to temporarily override a wrong stored passphrase. Fixed in Cockpit version 125 |
Created attachment 1196595 [details] screenshot Description of problem: Version-Release number of selected component (if applicable): cockpit-0.117-1.fc25.x86_64 How reproducible: always Steps to Reproduce: 1.add a disk using virt-manager after do a clean install 2.create a luks partition using cockpit 3.click on "Encryption Options" in the drop list of lock 4.change the stored passphrase and click "Apply" 5.click "lock" to lock the partition 6.click "unlock" and input the new passphrase,got the error shown in the picture 7.got the same result with the old passphrase,which works well before I changed the passphrase Actual results: Expected results: Additional info: