ProvisioningError :blkid returns with Exit code:2

[metal3-io]

ProvisioningError :blkid returns with Exit code:2

[dtantsur]

I've just reproduced this exact error when using an HTML page instead of a proper image. Maybe your image got corrupted as well? I'll work on better diagnostics.

[dtantsur]

I tried using this(http://cloud-images.ubuntu.com/releases/focal/release/ubuntu-20.04-server-cloudimg-amd64.img) image

I've just managed to successfully provision from this image using pure Ironic (not Metal3).

[dtantsur]

I see in your logs for node-4:

Image streamed onto device /dev/vda in 0.055956125259399414 seconds

0.05 seconds is a suspicious time for the image to be downloaded and written. Could you double-check what http://172.22.0.160/images/UBUNTU_20.04_NODE_IMAGE_K8S_v1.22.0-raw.img actually is?

P.S.
Also please avoid putting logs in a docx file, just a text file is enough.

[wcecs]

httpd container logs

172.22.0.197 - - [05/Sep/2021:07:27:05 +0000] "GET /images/UBUNTU_20.04_NODE_IMAGE_K8S_v1.22.0-raw.img.md5sum HTTP/1.1" 200 33 "-" "python-requests/2.25.1"
172.22.0.197 - - [05/Sep/2021:07:27:05 +0000] "GET /images/UBUNTU_20.04_NODE_IMAGE_K8S_v1.22.0-raw.img HTTP/1.1" 200 1024 "-" "python-requests/2.25.1"

1024(too small) means the file is not getting correctly downloaded, I think so.

[dtantsur]

Check the file that you have with file or qemu-img. This is for a real qcow2 image:

$ file /httpboot/deployment_image.qcow2
/httpboot/deployment_image.qcow2: QEMU QCOW Image (v3), 117440512 bytes

$ qemu-img info /httpboot/deployment_image.qcow2
image: /httpboot/deployment_image.qcow2
file format: qcow2
virtual size: 112 MiB (117440512 bytes)
disk size: 15.6 MiB
cluster_size: 65536
Format specific information:
    compat: 1.1
    lazy refcounts: false
    refcount bits: 16
    corrupt: false

[wcecs]

I tried using this(http://cloud-images.ubuntu.com/releases/focal/release/ubuntu-20.04-server-cloudimg-amd64.img) image using ironic CLI (succeeded). Not able to provision using provisioning scripts and with ironic CLI using default image metal3 uses.

[metal3-io-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[metal3-io-bot]

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

[metal3-io-bot]

@metal3-io-bot: Closing this issue.

In response to this:

Stale issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle stale.

/close

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/test-infra repository.