Deploying VM with Discovery: sda failed to get path uid

Support
1

Problem:

On deploying a VM using Foreman + Discovery on an ESXi-VM I am getting sda failed to get path uid

2020-11-04 09_56_00-hts-sys-dl1
2020-11-04 09_56_00-hts-sys-dl11635Ă—921 358 KB

Expected outcome:
Normal installation

Foreman and Proxy versions:

Discovery

Version

1.0.5

Dynflow

Version

0.2.4

HTTPBoot

Version

1.24.3

SSH

Version

0.2.1

TFTP

Version

1.24.3

TFTP server

false

Templates

Version

1.24.3

Distribution and version:

CentOS7

2

When/where do you see this? On the discovered node? Anaconda installer? After installation?

Are you sure about this version? That should be 16.0 for this Foreman release.

3

I get this error after I provisioned the host from the foreman’s discovered hosts page. This kills the installation process and the installer exits into dracut.

The “waiting for kexec into installer” disappears and right after this I am getting the result you see in my screenshot.

Ah, sorry. I took the version from the smart-proxie’s details page.

This is the correct version: 16.0.1

4

KExec does not work reliably on VMWare as well as other environments. If you can’t afford PXE, then use Bootdisk with VMWare integration.

5

For others that come accross this issue, VMWare doesn’t provide disk UUID’s by default. You can enable this feature though, by adding the config key/value: disk.EnableUUID = TRUE. The downside, as I understand it, is that it will limit your ability to clone the VM.

1 Like
6

Oh intereting, thanks for letting us know!

1 Like