I tracked down the following change introduced in Pike that is causing the "reload ioctl on (254:5) failed: No data available" tempest failures: https://review.openstack.org/#/c/488264
The problem seems to be that the snapshot volume is not active when the snapshot volume is created. Another easy way to reproduce this is to create the volume snapshot manually:
I tracked down the following change introduced in Pike that is causing the "reload ioctl on (254:5) failed: No data available" tempest failures: https:/ /review. openstack. org/#/c/ 488264
The problem seems to be that the snapshot volume is not active when the snapshot volume is created. Another easy way to reproduce this is to create the volume snapshot manually:
openstack volume create --size 1 test-volume volume
openstack snapshot create --name test-snapshot test-volume
openstack volume create --snapshot test-snapshot --size 2 test-snapshot-
If I manually activate the snapshot before running the third step, cinder-volume doesn't complain anymore.