-
Notifications
You must be signed in to change notification settings - Fork 162
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
Invalid node pool type, only support vm and ElasticBMS #548
Comments
@Jason-Zhang9309 please have a look at this! |
This problem has been fixed with pr #554 . A new required parameter "type" was added. Possible values are: "vm" and "ElasticBMS". |
Error: Unsupported argument on main.tf line 57, in resource "huaweicloud_cce_node_pool" "node_pool": An argument named "type" is not expected here. |
@kittitucht We found out that it was an API problem. They have fixed it. So your tf script could be useful. Don't add "type", and try again. |
@Jason-Zhang9309 still got the error |
@kittitucht which region are you using? |
@niuzhenguo I'm using region ap-southeast-2 |
@kittitucht That's an API side issue, please create a ticket on Cloud side if it still exists. |
@niuzhenguo I have raised it on Cloud side, but they said that the API can create a node pool |
@kittitucht Do you still face the same problem? If it's not fixed on the Cloud side till now, you can try our new release v1.19.1 which added a new |
I have tried a new release of v1.19.1 and it fixes the problem. Thank you very much. |
resource "huaweicloud_cce_node_pool" "node_pool" {
cluster_id = huaweicloud_cce_cluster.mycluster1.id
name = "testpool"
os = "EulerOS"
initial_node_count = 2
flavor_id = "s3.large.2"
password = "JDYkS1oydTcxQ0Q0SmpRbmVBeSRXRjVkc29PalRnYzlSRDQ2aTQ2Y0NMM0g5MkxNRW83OHMwckhkZlNMREU4UFc3eWxFMklDY3hVR0Y3LzhSQmJueFcwY3JnQTNaR05GQTBMTGdGYVlEMA=="
scall_enable = true
min_node_count = 1
max_node_count = 10
scale_down_cooldown_time = 100
priority = 1
root_volume {
size = 40
volumetype = "SAS"
}
data_volumes {
size = 100
volumetype = "SAS"
}
}
failed with error message of
Invalid node pool type, only support vm and ElasticBMS
The text was updated successfully, but these errors were encountered: