Skip to content
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

nutanix.ncp.ntnx_vms when clone disk from image device file sys_wwid pvid last seen on /dev/sd# not found #507

Open
darthVikes opened this issue Sep 26, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@darthVikes
Copy link

darthVikes commented Sep 26, 2024

Describe the bug

When using the nutanix.ncp.ntnx_vms function and clone_image from the disk image getting :

"Device file sys_wwid t10.NUTANIX.NFS_3_0_UUID Last seen on /dev/sdb not found"

During Linux boot, this is RHEL 9.x

To Reproduce

Steps to reproduce the behavior:
ansible-playbook playbook.yaml

    - name: Create VM
      nutanix.ncp.ntnx_vms:
        state: present
        name: "ansible_automation_demo"
        desc: "ansible_vm_description"
        cluster:
          name: "{{ ntnx_cluster }}"
        networks:
          - is_connected: true
            subnet:
              name: "{{ subnet_name }}"
              cluster:
                name: "{{ ntnx_cluster }}"
        disks:
          - type: "DISK"
            size_gb: 1
            bus: "SCSI"
            clone_image:
              name: "{{ image_name }}"
          - type: "DISK"
            size_gb: 50
            bus: "SCSI"
            clone_image:
              name: "{{ image_name }}-disk2"
          - type: "DISK"
            size_gb: 5
            bus: "SCSI"
            clone_image:
              name: "{{ image_name }}-disk3"

/boot = sda
/ = sdb
/data = sdc

Stack trace
image

Expected behavior
It would find the disk, and boot.

@darthVikes darthVikes added the bug Something isn't working label Sep 26, 2024
@darthVikes
Copy link
Author

Apparently this is a RH Feature for RHEL 9. Although, RH also says the cloning software should clean up any old PVIDs in the file. So not sure if that is possible with this Ansible module?

One other option is that you can disable it by:

  • use_devicesfile=0 in /etc/lvm/lvm.conf
  • rm /etc/lvm/devices/system.devices
  • reboot

Documentation

@darthVikes
Copy link
Author

More here also: RH KB: 7029161:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants