-
Notifications
You must be signed in to change notification settings - Fork 107
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
Having secondary storage class reports 'did not have enough free storage'. #489
Comments
Confirmed that this issue only occurs when using a custom nodeid value. |
@DeprecatedLuke Can you please share the yaml file where you are using custom nodeid ? |
|
Can you try with the latest master now as PR #451 is merged. |
As I mentioned before I don't have this configuration setup anymore as I migrated the pv nodeid's by modifying ZFSVolume and recreating pvc's. But I can assume this is fixed since it was most likely mapping to a node which was no longer online. |
What steps did you take and what happened:
Creating a secondary storage class 'large' seems to be very broken. It clearly shows that the capacity is available, but the scheduler is reporting 'did not have enough free storage'. This works just fine when using 'standard' storage class.
Failing line:
What did you expect to happen:
Pod to schedule normally.
The output of the following commands will help us better understand what's going on:
Anything else you would like to add:
Environment:
The text was updated successfully, but these errors were encountered: