New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't Install Minishift: Pre-flight check for persistent storage volume shows "Insufficient disk space" #1923

Closed
karlnicholas opened this Issue Jan 18, 2018 · 14 comments

Comments

Projects
None yet
4 participants
@karlnicholas
Contributor

karlnicholas commented Jan 18, 2018

  • Minishift version: 1.11.0
  • Windows 10 Home - Version 1709 - Build 16299.125 (up to date)
  • VirtualBox - Version 5.2.6 r120293 (Qt5.6.2)
  1. Download Minishift
  2. Run minishift start --vm-driver=virtualbox
    It ran OK once I think last week, and worked all day, but then the problem happened again the next day.
    This happened again just now:
C:\Users\karln>minishift start --vm-driver=virtualbox
-- Starting profile 'minishift'
-- Checking if requested hypervisor 'virtualbox' is supported on this platform ... OK
-- Checking if VirtualBox is installed ... OK
-- Checking the ISO URL ... OK
-- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
-- Minishift VM will be configured with ...
   Memory:    2 GB
   vCPUs :    2
   Disk size: 20 GB

   Downloading ISO 'https://github.com/minishift/minishift-b2d-iso/releases/download/v1.2.0/minishift-b2d.iso'
 40.00 MiB / 40.00 MiB [===================================================================================] 100.00% 0s
-- Starting Minishift VM ............................ OK
-- Checking for IP address ... OK
-- Checking if external host is reachable from the Minishift VM ...
   Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ...
   Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... warning:
 used FAIL
   Insufficient disk space on the persistent storage volume

virtualbox_minishift_18_01_2018_13_08_20

@gbraad

This comment has been minimized.

Member

gbraad commented Jan 19, 2018

Please check the documentation on how to handle this situation:

https://docs.openshift.org/latest/minishift/troubleshooting/troubleshooting-getting-started.html#persistent-storage-check

Depending on the hypervisor you need to either enlarge the disk, or choose to copy data out and recreate with a larger size. We are not able to perform the changing of the disk size.

@gbraad

This comment has been minimized.

Member

gbraad commented Jan 19, 2018

Marking as invalid, as this works 'as expected'. When the disk is full, unpredictible behaviour will occur, and with this check we want to inform the user beforehand.

We might want to include a link or reference to the troubleshooting segment in the error.

@gbraad gbraad changed the title from Minishift - Windows 10 - Insufficient disk space on the persistent storage volume to Pre-flight check for persistent storage volume shows "Insufficient disk space" Jan 19, 2018

@budhram budhram added this to the v1.14.0 milestone Jan 19, 2018

@budhram

This comment has been minimized.

Member

budhram commented Jan 19, 2018

We might want to include a link or reference to the troubleshooting segment in the error.

Sure. Hence, changed the labels.

@karlnicholas karlnicholas changed the title from Pre-flight check for persistent storage volume shows "Insufficient disk space" to Can't Install Minishift: Pre-flight check for persistent storage volume shows "Insufficient disk space" Jan 19, 2018

@karlnicholas

This comment has been minimized.

Contributor

karlnicholas commented Jan 19, 2018

Detailed log of disk check space using

minishift start --vm-driver virtualbox --show-libmachine-logs -v5

-- Checking available disk space ... (minishift) Calling .GetSSHHostname
(minishift) Calling .GetSSHPort
(minishift) Calling .GetSSHKeyPath
(minishift) Calling .GetSSHKeyPath
(minishift) Calling .GetSSHUsername
Using SSH client type: external
&{[-F /dev/null -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none docker@127.0.0.1 -o IdentitiesOnly=yes -i C:\Users\karln\.minishift\machines\minishift\id_rsa -p 65245] C:\Program Files\OpenShift\bin\ssh.exe <nil>}
About to run SSH command:
df -h /mnt/sda1 | awk 'FNR > 1 {print $2,$5}'
SSH cmd err, output: <nil>: cygwin warning:
  MS-DOS style path detected: C:\Users\karln\.minishift\machines\minishift\id_rsa
  Preferred POSIX equivalent is: /cygdrive/c/Users/karln/.minishift/machines/minishift/id_rsa
  CYGWIN environment variable option "nodosfilewarning" turns off this warning.
  Consult the user's guide for more details about POSIX paths:
    http://cygwin.com/cygwin-ug-net/using.html#using-pathnames
17.9G 0%

warning:
 used FAIL
   Insufficient disk space on the persistent storage volume

@karlnicholas

This comment has been minimized.

Contributor

karlnicholas commented Jan 19, 2018

Okay, I'm pretty sure I found the problem. I Set CYGWIN=nodosfilewarning in my environment because without it the SSH I have install was generating some kind of warning. Minishift seems to be installed and running OK now.

-- Checking available disk space ... (minishift) Calling .GetSSHHostname
(minishift) Calling .GetSSHPort
(minishift) Calling .GetSSHKeyPath
(minishift) Calling .GetSSHKeyPath
(minishift) Calling .GetSSHUsername
Using SSH client type: external
&{[-F /dev/null -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none docker@127.0.0.1 -o IdentitiesOnly=yes -i C:\Users\karln\.minishift\machines\minishift\id_rsa -p 49174] C:\users\karln\OpenShift\bin\ssh.exe <nil>}
About to run SSH command:
df -h /mnt/sda1 | awk 'FNR > 1 {print $2,$5}'
SSH cmd err, output: <nil>: 17.9G 0%

0% used OK

@gbraad

This comment has been minimized.

Member

gbraad commented Jan 19, 2018

@gbraad

This comment has been minimized.

Member

gbraad commented Jan 19, 2018

@gbraad

This comment has been minimized.

Member

gbraad commented Jan 19, 2018

@karlnicholas

This comment has been minimized.

Contributor

karlnicholas commented Jan 20, 2018

the ssh.exe "installed" was from cwrsync which I added to the OC bin directory so that I could use rsync with OC to manage my permanent stores on openshift. (https://www.itefix.net/content/cwrsync-free-edition). I just DL's those binaries and copied them into the openshift/bin directory. I don't have ssh installed in Cygwin but maybe the cwrsync version uses a copy of that binary or something.

Actually, I have just DL'd the redhat Container Development Kit Version (CDK) of minishift (https://developers.redhat.com/download-manager/file/cdk-3.2.0-1-minishift-windows-amd64.exe) so that I can use all this in DevStudio, and it's all working OK now. Personally, I'm good to go and I probably saw it all working once when I initially installed the DevStudio CDK Bundle which comes with cygwin and then changed things back to my own installation of Cygwin and got hung up on the SSH issue. Sorry for the confusion -- possibly another fix might be to have the Cygwin binaries in your path and be sure SSH is installed there.

There is a another version of SSH I have which is Microsoft's beta SSH you can get by adding features in Windows/Setup but that's later in the PATH and so doesn't get executed. I didn't try it to see if it ran the minishift installation correctly.

@karlnicholas

This comment has been minimized.

Contributor

karlnicholas commented Jan 20, 2018

In terms of setting the test to skip I had tried that but still had problems. I presume again that wherever the installation was checking the results from the SSH I was using was failing and so still giving problems.

Probably I'll "bite the bullet" and install ssh.exe in Cygwin and delete the weird one I ended up DL'ing.

@gbraad

This comment has been minimized.

Member

gbraad commented Jan 20, 2018

@karlnicholas

This comment has been minimized.

Contributor

karlnicholas commented Jan 20, 2018

Right - It's not obvious in the documentation anywhere that minishift depends on an installed SSH application and since it's an executable you tend to think it has everything it needs built in. This would go well on the front page.

Also, it might be a good idea to set the CYGWIN=nodosfilewarning env variable when running, if possible. I think the issue is that the proper Cygwin SSH has it defaulted to (no)dosfilewarning and the version I picked up has it defaulted to on for some reason. I don't think it can hurt anything. Perhaps I can submit a pull request but I'm not sure where to start looking for setting initial variables. Thanks for the follow-up.

Good to know about the SSH beta but I deleted it anyway because it doesn't support rsa.

@gbraad

This comment has been minimized.

Member

gbraad commented Jan 25, 2018

We do not need to have SSH installed, as we can fall back to a SSH-implementation inside the minishift executable. However, as soon as an ssh.exe is detected on PATH, we use that instead. On Linux or macOS this 'never' causes an issue, but having a plethora of options of ssh clients on Windows creates a problem for us while testing. So, yes... we have some issues to add supported SSH clients to the documentation. it would be great to see a PR ;-)

@LalatenduMohanty

This comment has been minimized.

Member

LalatenduMohanty commented Jan 31, 2018

Resolved by #1952

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment