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
Creating new LV in existing VG requires specifying disk #96
Milestone
Comments
Actual output with errors:
|
It does work successfully if I add - hosts: all
remote_user: root
# become: yes
# become_method: sudo
# become_user: root
vars:
tasks:
- name: create some test storage
include_role:
name: linux-system-roles.storage
vars:
storage_pools:
- name: fedora_alderaan
disks: ['sda3']
# type: lvm
state: present
volumes:
- name: test
size: "1G"
# type: lvm
# fs_type: xfs
fs_label: "test"
mount_point: '/mnt/test' Results after successful run
|
So the request is to interpret a pool w/ no disks as a lookup by whatever information is provided? That's pretty reasonable, but understand that it will be unusable when the pool isn't pre-existing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I want to create a new LV in an existing VG. I would like it to assume the existing setup and only specify the new things to add.
Today, I do this with a simple lvcreate command to create a new LV in an existing VG. I only need to provide the VGname, LVname, and size:
lvcreate -L1G -s -n /dev/virtual-machines/ha1-snapshot /dev/virtual-machines/ha1
However, this does not seem to work with the following playbook, as it errors suggesting it cannot lookup the disks.
The text was updated successfully, but these errors were encountered: