VMWare driver mount broken in 1.23

[zarenner]

Upgraded to 1.23 and driver mounts in VMWare Fusion appear to be broken. The /mnt/hgfs folder is entirely missing, and vmhgfs-fuse utility is missing.

Steps to reproduce the issue:

1. minikube start --iso-url=https://storage.googleapis.com/minikube/iso/minikube-v1.23.0.iso --driver=vmware
2. minikube ssh
3. ls /mnt/hgfs returns No such file or directory
4. vmhgfs-fuse doesn't exist in /usr/bin/ Exists and works in v1.22.

While this seems potentially related to #12268 (/cc @afbjorklund), it's not obvious to me why vmhgfs-fuse went missing. BR2_PACKAGE_OPENVMTOOLS=y is still set, so perhaps it's something in https://github.com/buildroot/buildroot/tree/2021.02.x/package/openvmtools or https://github.com/vmware/open-vm-tools itself.

I'm not able to successfully build the ISO on macOS otherwise I'd investigate further.

[RA489]

/kind support

[dsedivec]

Having this here too. I did see this in the logs:

$ journalctl|grep -i hg
Sep 12 23:21:00 minikube sudo[4945]:   docker : PWD=/ ; USER=root ; COMMAND=/usr/bin/mount --bind /mnt/hgfs//hosthome /hosthome
Sep 12 23:21:00 minikube sudo[4948]:   docker : PWD=/ ; USER=root ; COMMAND=/usr/bin/mount -t vmhgfs -o uid=1000,gid=1000 .host:/Users /hosthome

Presumably that last would work if the vmhgfs kernel module was available—but open-vm-tools says that's been deprecated in favor of vmhgfs-fuse, as zarenner said.

[afbjorklund]

The kernel was kept back, so it should not be related to that (upgrading from Linux 4 to Linux 5, that is)

[Thracky]

Based on the makefile for the openvmtools package (https://github.com/buildroot/buildroot/blob/2021.02.x/package/openvmtools/openvmtools.mk) it looks like vmblock-fuse isn't enabled if BR2_PACKAGE_LIBFUSE isn't selected somewhere.

There are a number of packages that do include it so maybe a package that was previously selected and included libfuse is either no longer present or no longer selects the libfuse package.

Edit: I can confirm that adding BR2_PACKAGE_LIBFUSE=y to minikube_defconfig resolves this.

[schwichtgit]

would you benefit from a PR adding BR2_PACKAGE_LIBFUSE=y back in?
openvmtools hgfs etc, work fine on my locally built minikube.iso (based on 24.0)

[schwichtgit]

PR #13000 should address this issue.

$ ls -al /mnt/hgfs
total 5
dr-xr-xr-x 1 root root 4192 Jan 6 21:24 .
drwxr-xr-x 4 root root 80 Jan 6 19:18 ..
drwxr-xr-x 1 root 80 160 Dec 7 23:39 Users

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[RA489]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[RA489]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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.