-
Notifications
You must be signed in to change notification settings - Fork 45
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
salt,tests: Allow forcing the creation of an LV #3877
Conversation
Hello gdemonet,My role is to assist you with the merge of this Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
95df02c
to
c38b6d4
Compare
ui/src/containers/CreateVolume.js
Outdated
<Input | ||
name="forceLVCreate" | ||
value={values.forceLVCreate} | ||
onChange={handleChange('forceLVCreate')} | ||
label={ | ||
<> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be a toggle.
ui/src/containers/CreateVolume.js
Outdated
</div> | ||
} | ||
> | ||
<InputWarning className="fas fa-triangle-exclamation"></InputWarning> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: fa-triangle-exclamation
icon is being deprecated in favor of fa-exclamation-circle
ui/src/containers/CreateVolume.js
Outdated
<Tooltip | ||
placement="right" | ||
overlay={ | ||
<div style={{ minWidth: '200px' }}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: the new form component is going to handle this, so you don't have to care about it
<div style={{ minWidth: '200px' }}> | |
<div style={{ minWidth: '80rem' }}> |
ui/src/containers/CreateVolume.js
Outdated
@@ -208,6 +208,10 @@ const InputQuestionMark = styled.i` | |||
color: ${(props) => props.theme.infoPrimary}; | |||
`; | |||
|
|||
const InputWarning = styled(InputQuestionMark)` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: InputWarning
implies that it would be an input component simply with color changing to warning
. However here it is the Icon that change. Moreover we have a new Icon
component in core-ui that should be used for this purpose. <Icon color='statusWarning' name='Exclamation-circle' />
9228cda
to
140a700
Compare
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
6a00bbb
to
fdf6c18
Compare
@@ -269,3 +269,36 @@ Feature: Volume management | |||
Then the Volume 'test-volume12-lvmlv' is 'Available' | |||
And the PersistentVolume 'test-volume12-lvmlv' has size '10Gi' | |||
And the device '/dev/test-vg-12/test-volume12-lvmlv' exists | |||
|
|||
Scenario: Test volume re-creation (lvmLogicalVolume force-lvcreate) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From the CI build it seems you got a failure on this test in 3-nodes (flaky ?, weird, I don't see how this test could be flaky and the one for the single node succeeded 😕 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I need to debug this, haven't had time yet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For reference: this was caused by an older version of LVM in CentOS 7, which doesn't prevent LV creation even if signatures were detected and not wiped. Added a note about this in the CHANGELOG, and skipped the test on CentOS 7 / RHEL 7 (actually, just testing the osmajorrelease
grain, but we only support RedHat-family OSes, so should be enough).
This comment was marked as resolved.
This comment was marked as resolved.
fdf6c18
to
bb28614
Compare
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
bb28614
to
b4b4965
Compare
6e58d5b
to
3a7f563
Compare
In case a formatted LV was removed without wiping its FS signature, creation from storage-operator will fail. We add support for an annotation (metalk8s.scality.com/force-lvcreate) to force the creation of the LV, at the risk of also wiping the previous FS contents.
3a7f563
to
e431996
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue None. Goodbye gdemonet. |
In case a formatted LV was removed without wiping its FS signature, creation from storage-operator will fail. We add support for an annotation (metalk8s.scality.com/force-lvcreate) to force the creation of the LV, at the risk of also wiping the previous FS contents.