You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to update a 3.7.0 cluster in the PC UI and can't get past the Head node page.
It is flagging the Root volume size as incorrect. It is 200GB and it says "You must use an integer >= 35GB for root volume size".
Last time I checked 200 >= 35.
Possibly a string not being correctly converted to integer.
If I look at the config YAML I see the following:
LocalStorage:
RootVolume:
Size: '200'
Note the single quotes which means it is a string, not an int.
The original config I deployed had it as an integer:
LocalStorage:
RootVolume:
Size: 200
Steps to reproduce the issue
I deployed via a lambda.
Expected behaviour
I can edit the cluster configuration in the UI.
Actual behaviour
Incorrectly flags the root volume size as invalid.
Required info
In order to help us determine the root cause of the issue, please provide the following information:
Region: us-east-1
Version of ParallelCluster UI: Where is this found
ParallelCluster: 3.7.0
Additional info
The following information is not required but helpful:
OS: Widows
Browser: firefox
If having problems with cluster creation or update
The text was updated successfully, but these errors were encountered:
Thank you for the detailed description. Can you confirm this is an issue that only occurs for clusters created with PC 3.7.0? (as opposed to, for instance PC 3.6.0). I was able to create and describe a cluster with RootVolume size 50 by using PCUI with PC 3.6.0
While I cannot share an ETA for a release with full support for PC 3.7.0, I am sharing this issue with the team
Description
Trying to update a 3.7.0 cluster in the PC UI and can't get past the Head node page.
It is flagging the Root volume size as incorrect. It is 200GB and it says "You must use an integer >= 35GB for root volume size".
Last time I checked 200 >= 35.
Possibly a string not being correctly converted to integer.
If I look at the config YAML I see the following:
Note the single quotes which means it is a string, not an int.
The original config I deployed had it as an integer:
Steps to reproduce the issue
I deployed via a lambda.
Expected behaviour
I can edit the cluster configuration in the UI.
Actual behaviour
Incorrectly flags the root volume size as invalid.
Required info
In order to help us determine the root cause of the issue, please provide the following information:
Additional info
The following information is not required but helpful:
If having problems with cluster creation or update
The text was updated successfully, but these errors were encountered: