[BUG] Can't use data disk measured in terabytes v1.2.1

[MikeTolkachev]

I'm trying to use 4TB nvme drive for data disk and i receive a message:
Disk size is to small. Minimum 100Gi is required.

[connorkuehl]

What size is your install disk?

[MikeTolkachev]

Disk is 120Gi (111 on picture).
Installation is available if I select the first disk (120) for both installation and data.

[tserong]

I've tried to reproduce this, and I believe you're seeing that error not because of the 4TiB data disk, but because the installation disk is too small. In my testing, v1.2.1 needs at least a 180GiB installation disk if you have a separate data disk.

Here's what I got when I tried a 4TiB data disk:

I realise that in your second screenshot (with the installation disk and data disk the same) it doesn't show an error, but what happens if you hit ENTER at that point to try to commence the install? In my case, I don't see an error immediately, but once I hit ENTER on the persistent size field, with a single 120GiB disk, I get the error "Disk size is too small. Minimum 250Gi is required":

[tserong]

Assuming I'm correct about the above, I suspect we need to make two changes:

1. For clarity, make the error say "Installation disk is too small", rather than "Disk is too small".
2. When using the installation disk for data, ensure the error message appears early, rather than waiting 'til the user hits ENTER at the end.

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

• If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
  The HEP PR is at:

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at: [e2e] [BUG] Can't use data disk measured in terabytes v1.2.1 tests#987

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
  The PR is at: console: validate disk size earlier, update error wording harvester-installer#596

  • Does the PR include the explanation for the fix or the feature?

  • Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
    The PR for the YAML change is at:
    The PR for the chart change is at:

• If labeled: area/ui Has the UI issue filed or ready to be merged?
  The UI issue/PR is at:

• If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
  The documentation/KB PR is at:

• If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at:

[harvesterhci-io-github-bot]

Automation e2e test issue: harvester/tests#987

[harvesterhci-io-github-bot]

added backport-needed/1.2.2 issue: #4793.

[irishgordo]

This looks good on v1.3.0-rc1 😄 👍
I'll go ahead and close this out: