Project

General

Profile

Bug #53595

Detach geli providers after locking pool

Added by Waqar Ahmed 10 months ago. Updated 5 months ago.

Status:
Done
Priority:
No priority
Assignee:
Waqar Ahmed
Category:
Middleware
Target version:
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.

lock5.png (24.4 KB) lock5.png Jeff Ervin, 04/03/2019 10:02 AM
lock6.png (28.1 KB) lock6.png Jeff Ervin, 04/03/2019 10:02 AM
lock4.png (38.8 KB) lock4.png Jeff Ervin, 04/03/2019 10:02 AM
lock2.png (21.9 KB) lock2.png Jeff Ervin, 04/03/2019 10:02 AM
lock1.png (32.7 KB) lock1.png Jeff Ervin, 04/03/2019 10:02 AM
lock3.png (26.2 KB) lock3.png Jeff Ervin, 04/03/2019 10:02 AM
63660
63667
63668
63676
63684
63691

Associated revisions

Revision d3d9e4f1 (diff)
Added by Waqar Ahmed 10 months ago

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

History

#1 Updated by Bug Clerk 10 months ago

  • Status changed from In Progress to Ready for Testing

#2 Updated by Dru Lavigne 10 months ago

  • Subject changed from Lock not detaching geli providers to Detach geli providers after locking pool
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#3 Updated by Dru Lavigne 7 months ago

  • Target version changed from 11.3 to 11.3-BETA1

#5 Updated by Jeff Ervin 5 months ago

63660
63667
63668
63676
63684
63691

Test Passed FreeNAS-11.3-MASTER-201904031032

Criteria followed. Test completed in both Legacy and WebUI

#6 Updated by Dru Lavigne 5 months ago

  • Status changed from Passed Testing to Done
  • Target version changed from 11.3-BETA1 to 11.3-ALPHA1

Also available in: Atom PDF