Bug #53595
Detach geli providers after locking pool
Seen in:
Severity:
Med High
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No
Description
When we lock a pool, it does not detach geli providers which results in undesired behaviour in both UI and the backend system as the system does not interpret it as a locked volume
Risk
We risk making the pool in question unusable
Acceptance Criteria
A pool should be made and then locked. After locking it should be ensured that the UI is not displaying any errors for the pool and is stating it as locked ( UI as in legacy UI ). Once that has been confirmed, the pool should then be unlocked and it should unlock as desired.
Associated revisions
History
Updated by Bug Clerk 
Updated by Dru Lavigne #5
Updated by Jeff Ervin 5 months ago
Updated by Jeff Ervin 
- File lock6.png lock6.png added
- File lock5.png lock5.png added
- File lock4.png lock4.png added
- File lock3.png lock3.png added
- File lock2.png lock2.png added
- File lock1.png lock1.png added
- Status changed from Ready for Testing to Passed Testing
- Needs QA changed from Yes to No
Test Passed FreeNAS-11.3-MASTER-201904031032
Criteria followed. Test completed in both Legacy and WebUI
Detach geli providers after locking pool
This commit ensures that after we have exported our pool while locking a pool, we detach the relevant geli providers.
Ticket: #53595