-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPVE-616: fix: add check of correct lv state of thin-pool when vg is already created #381
OCPVE-616: fix: add check of correct lv state of thin-pool when vg is already created #381
Conversation
@jakobmoellerdev: This pull request references OCPVE-616 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
5ff455e
to
32ba0c2
Compare
32ba0c2
to
aa76c61
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #381 +/- ##
===========================================
+ Coverage 16.59% 55.69% +39.09%
===========================================
Files 24 26 +2
Lines 2061 2223 +162
===========================================
+ Hits 342 1238 +896
+ Misses 1693 896 -797
- Partials 26 89 +63
|
aa76c61
to
af7e600
Compare
af7e600
to
d270241
Compare
d270241
to
aeb67cc
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jakobmoellerdev, suleymanakbas91 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test lvm-operator-e2e-aws |
@jakobmoellerdev: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
This introduces new checks when the LV was already created as a thin pool to ensure correct status updates even after the VG was setup initially.
Checks include:
Metadata space exhaustion can lead to inconsistent thin pool metadata and inconsistent file systems, so the response requires offline checking and repair.
), allowing users to still circumvent withlvextend --poolmetadatasize
in case of overprovisioning. This allow users to avoid having to reboot the node and repair the deactivated LV