The image can be converted and mounted using nbd just fine on my system.
On my system I see this logged in dmesg when connecting the nbd device:
[146056.667136] nbd0: detected capacity change from 0 to 10547200
And then this in dmesg when mounting the filesystem:
[146078.599160] XFS (nbd0): Mounting V5 Filesystem 19d3e5c1-45f0-43f4-8cad-ee89fb197cdb
[146078.606937] XFS (nbd0): Ending clean mount
I tried to reproduce this using - https:/ /images. rdoproject. org/centos8/ train/rdo_ trunk/tripleo- ci-testing/ overcloud- full.tar
The image can be converted and mounted using nbd just fine on my system.
On my system I see this logged in dmesg when connecting the nbd device:
[146056.667136] nbd0: detected capacity change from 0 to 10547200
And then this in dmesg when mounting the filesystem: 45f0-43f4- 8cad-ee89fb197c db
[146078.599160] XFS (nbd0): Mounting V5 Filesystem 19d3e5c1-
[146078.606937] XFS (nbd0): Ending clean mount
I cannot see anything related to nbd in: /logserver. rdoproject. org/openstack- periodic- integration- stable4/ opendev. org/openstack/ tripleo- ci/master/ periodic- tripleo- ci-centos- 8-ovb-3ctlr_ 1comp-featurese t035-train/ 72722f2/ logs/undercloud /var/log/ extra/dmesg. txt.gz
https:/
Can we reproduce and hold the node?