Configure LVM's devices file #1046
Conversation
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/bd3f56c9edc94622aae11e56d0cf50d6 ✔️ openstack-k8s-operators-content-provider SUCCESS in 3h 25m 33s |
|
@gibizer any idea why this failed? https://softwarefactory-project.io/zuul/t/rdoproject.org/build/884e03c6657a4371a8db18e9e842cab5 |
|
Same failure on another of my edpm-ansible PRs, https://softwarefactory-project.io/zuul/t/rdoproject.org/build/88aff6706c2c4e1fb9ef711b19f754d1 |
Configure LVM's "devices file" in order to prevent it from scanning cinder volume attachments. LVM uses the concept of a devices file to control whether it scans local and dynamically attached (SAN) volumes. This is an enhancement over using LVM device filters. The devices file essentially provides a whitelist of devices that should be scanned, and the file is automatically updated by LVM commands such as 'lvcreate'. For this to work, the devices file must exist even if it's empty. Resolves: OSPRH-20217 Signed-off-by: Alan Bishop <[email protected]>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ASBishop, slagle 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 |
openshift-merge-bot
bot
merged commit e305edf
into
openstack-k8s-operators:main
|
/cherry-pick 18.0-fr4 |
|
@tosky: new pull request created: #1061 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-sigs/prow repository. |
4 participants
Configure LVM's "devices file" in order to prevent it from scanning cinder volume attachments.
LVM uses the concept of a devices file to control whether it scans local and dynamically attached (SAN) volumes. This is an enhancement over using LVM device filters. The devices file essentially provides a whitelist of devices that should be scanned, and the file is automatically updated by LVM commands such as 'lvcreate'. For this to work, the devices file must exist even if it's empty.
Resolves: OSPRH-20217