local blockdevice

[kfox1111]

I tried to use a local volume block device in minikube. Its trying to call losetup with the -j option and its failing as the losetup in minikube does not provide this option. This may effect other distro's as well. The end result is lock block devices don't work on the platform.

[kfox1111]

/sig storage

[pohly]

Probably caused by this code:

kubernetes/pkg/volume/util/volumepathhandler/volume_path_handler_linux.go

Lines 50 to 60 in 86dbdbe

	// GetLoopDevice returns the full path to the loop device associated with the given path.
	func (v VolumePathHandler) GetLoopDevice(path string) (string, error) {
	_, err := os.Stat(path)
	if os.IsNotExist(err) {
	return "", errors.New(ErrDeviceNotFound)
	}
	if err != nil {
	return "", fmt.Errorf("not attachable: %v", err)
	}
	args := []string{"-j", path}

[kfox1111]

Did a strace on losetup -j. looks like the same info can be had by:
cat /sys/block/loop0/loop/backing_file

[irizzant]

Just had the same problem with Ceph cluster creation in minikube, the osd-prepare doesn't start because of this:

Events:
  Type     Reason           Age                 From               Message
  ----     ------           ----                ----               -------
  Normal   Scheduled        2m2s                default-scheduler  Successfully assigned rook-ceph/rook-ceph-osd-prepare-set1-0-data-sgpq7-j8tf9 to minikube
  Warning  FailedMapVolume  58s (x8 over 2m2s)  kubelet, minikube  MapVolume.MapBlockVolume failed for volume "local-pv-c84df416" : blkUtil.AttachFileDevice failed. globalMapPath:/var/lib/kubelet/plugins/kubernetes.io~local-volume/volumeDevices/local-pv-c84df416, podUID: a477949a-a571-47ef-8409-6f8a3404dc64: GetLoopDevice failed for path /var/lib/kubelet/plugins/kubernetes.io~local-volume/volumeDevices/local-pv-c84df416/a477949a-a571-47ef-8409-6f8a3404dc64: losetup -j /var/lib/kubelet/plugins/kubernetes.io~local-volume/volumeDevices/local-pv-c84df416/a477949a-a571-47ef-8409-6f8a3404dc64 failed: exit status 1

[mwennrich]

FYI: https://github.com/kubernetes-csi/csi-driver-host-path has the same problem in minikube. Replacing the /sbin/losetup busybox link with a "real" losetup helped for now, but isn't a solution of course.

[fejta-bot]

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

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[irizzant]

/remove-lifecycle rotten

[fejta-bot]

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

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[irizzant]

/remove-lifecycle stale

[fejta-bot]

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

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

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[irizzant]

/remove-lifecycle stale

[fejta-bot]

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

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

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[irizzant]

/remove-lifecycle stale

[pohly]

/help

[k8s-ci-robot]

@pohly:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.