Skip to content

hypervisor disk2 to use more resilient UUID than disk name #764

@afcollins

Description

@afcollins

On machines where there may be more than one of a disk type, using only the disk name (ex. 'sdb') could change after reboots.

The assumption for the hybrid workers hypervisor setup is to use the nvme disk, which there is usually only one attached to most scalelab machines.

However, if we want to use an SSD, which there can be two attached, the initial install could use 'sdb', but then after a reboot the disks may change and VMs will fail start due to their image not being found.

Ideal solution:

It would be ideal to allow the user to specify a secondary disk like 'sdb' for the initial install, then fetch the disk's UUID to template into fstab. This approach is persistent across reboots.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions