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
This is a bug that needs to be filed with the Marketplace/Deployment Manager team.
I receive the following error when I attempt to pass the cluster version as a string to the cluster.py file.
I've tried a couple of different iterations to ensure that clusterVersion is a string when its passed to cluster.py, but it continues to generate the error above.
In spite of this configuration it continues to generate the error above. I've seen a similar error for a different property before, and it seems that there is some bug related to type handling in Jinja/Python.
However, it works when I remove clusterVersion from the datashare-vm.jinja file.
As long as I don't set the clusterVersion within datashare-vm.jinja, then the default version (1.18) listed in the cluster.py.schema file is used and the correct data type appears to be correct as well.
The current workaround is to update the default cluster version in the cluster.py.schema file until Deployment Manager team resolves the bug.
The text was updated successfully, but these errors were encountered:
This is a bug that needs to be filed with the Marketplace/Deployment Manager team.
I receive the following error when I attempt to pass the cluster version as a string to the cluster.py file.
I've tried a couple of different iterations to ensure that clusterVersion is a string when its passed to cluster.py, but it continues to generate the error above.
clusterVersion is marked as a string in cluster.py.schema.
I pass the cluster version from datashare-vm.jinja as shown below.
clusterVersion is set as:
In spite of this configuration it continues to generate the error above. I've seen a similar error for a different property before, and it seems that there is some bug related to type handling in Jinja/Python.
However, it works when I remove
clusterVersion
from thedatashare-vm.jinja
file.As long as I don't set the
clusterVersion
withindatashare-vm.jinja
, then the default version (1.18) listed in thecluster.py.schema
file is used and the correct data type appears to be correct as well.The current workaround is to update the default cluster version in the
cluster.py.schema
file until Deployment Manager team resolves the bug.The text was updated successfully, but these errors were encountered: