Closed greyhoundforty closed 6 years ago
Hi, One of the reason for the exception could be unavailability of servers on the location wdc07. It works normal on locations where the servers are up/available like wdc04, dal06 etc.. Could you please try on locations wdc04, dal06.
All 4 of the VSIs got provisioned correctly and are up and online. I will test again though in wdc04.
Yeah, the error remains the same:
Error applying plan:
1 error(s) occurred:
* ibm_lbaas.lbaas: 1 error(s) occurred:
* ibm_lbaas.lbaas: Error during creation of Load balancer: SoftLayer_Exception_Public: The price for Load Balancer Uptime (#205913) is not valid for location wdc04. (HTTP 500)
The VSIs are provisioned properly:
$ slcli --format raw vs list -d wdc04 -D cde.services
41258523 host1 NULL 10.149.214.8 wdc04 NULL
41258529 host2 NULL 10.149.214.42 wdc04 NULL
41259311 host3 NULL 10.149.214.49 wdc04 NULL
41259309 host4 NULL 10.149.214.44 wdc04 NULL
Here is the updated main.tf
Ok.. Need some more information to proceed . Could you please enable the trace and run the terraform apply. For enabling trace export TF_LOG=trace
Could you please share me the output of these API calls
curl -g -k -L -H 'Content-Type: application/json' -u
curl -g -k -L -H 'Content-Type: application/json' -u
Replace the $packageidentifier
with id
from the output of first curl request
SoftLayer_Exception_Public: The price for Load Balancer Uptime (#205913) is not valid for location wdc04. (HTTP 500)
Interestingly I don't see the price id 205913 in the output of https://api.softlayer.com/rest/v3.1/SoftLayer_Product_Package/805/getItemPrices.
Output of terraform apply with TF_LOG=TRACE
curl -g -k -L -H 'Content-Type: application/json' -u "$SOFTLAYER_USERNAME:$SOFTLAYER_API_KEY" 'https://api.softlayer.com/rest/v3.1/SoftLayer_Product_Package/getAllObjects.json?objectMask=id;name;type&objectFilter={%22name%22:{%22operation%22:%22Load%20Balancer%20As%20A%20Service%20(LBaaS)%22}}'
[{"id":805,"name":"Load Balancer As A Service (LBaaS)","type":{"id":662,"keyName":"LOAD_BALANCER_AS_A_SERVICE","name":"Load Balancer As A Service"}}]%
curl -g -k -L -H 'Content-Type: application/json' -u "$SOFTLAYER_USERNAME:$SOFTLAYER_API_KEY" "https://api.softlayer.com/rest/v3.1/SoftLayer_Product_Package/805/getItemPrices?objectMask=id;item.description;categories.id"
[{"id":205915,"categories":[{"id":1119}],"item":{"description":"Load Balancer Uptime"}},{"id":205907,"categories":[{"id":1119}],"item":{"description":"Load Balancer Uptime"}},{"id":199467,"categories":[{"id":1117}],"item":{"description":"Load Balancer Bandwidth"}},{"id":205839,"categories":[{"id":1228}],"item":{"description":"Load Balancer Data Processed "}},{"id":205909,"categories":[{"id":1119}],"item":{"description":"Load Balancer Uptime"}},{"id":205917,"categories":[{"id":1119}],"item":{"description":"Load Balancer Uptime"}},{"id":205913,"categories":[{"id":1119}],"item":{"description":"Load Balancer Uptime"}},{"id":199447,"categories":[{"id":1116}],"item":{"description":"Load Balancer as a Service"}},{"id":205911,"categories":[{"id":1119}],"item":{"description":"Load Balancer Uptime"}}]%
This is an internal SoftLayer account (I work in Cloud Design Engineering) and was part of the beta. Not sure if the internal account part is causing an issue. Seems to only be affecting the LBaaS stuff at the moment as I can create VSIs and DNS records without issue.
Thanks for the logs: This is from your logs and it has 205913 price id. 2017-10-09T11:33:13.789Z [DEBUG] plugin.terraform-provider-ibm: 2017/10/09 11:33:13 [DEBUG] Request URL: GET https://api.softlayer.com/rest/v3/SoftLayer_Product_Package/805/getItems.json?objectMask=mask%5Bid%2Ccapacity%2Cdescription%2Cunits%2CkeyName%2Cprices%5Bid%2Ccategories%5Bid%2Cname%2CcategoryCode%5D%5D%5D 2017-10-09T11:33:13.789Z [DEBUG] plugin.terraform-provider-ibm: 2017/10/09 11:33:13 [DEBUG] Parameters: 2017-10-09T11:33:14.258Z [DEBUG] plugin.terraform-provider-ibm: 2017/10/09 11:33:14 [DEBUG] Response: [{"description":"Load Balancer Data Processed ","id":10771,"keyName":"LOAD_BALANCER_DATA_PROCESSED","units":"GIGABYTE","prices":[{"id":205839,"categories":[{"categoryCode":"load_balancer_data_processed","id":1228,"name":"Load Balancer Data Processed"}]}]},{"capacity":"0","description":"Load Balancer as a Service","id":10043,"keyName":"LOAD_BALANCER_AS_A_SERVICE","prices":[{"id":199447,"categories":[{"categoryCode":"load_balancer_as_a_service","id":1116,"name":"Load Balancer As A Service"}]}]},{"capacity":"0","description":"Load Balancer Bandwidth","id":10051,"keyName":"LOAD_BALANCER_BANDWIDTH","units":"GB","prices":[{"id":199467,"categories":[{"categoryCode":"load_balancer_bandwidth","id":1117,"name":"Load Balancer Bandwidth"}]}]},{"capacity":"0","description":"Load Balancer Uptime","id":10785,"keyName":"LOAD_BALANCER_UPTIME","units":"hour","prices":[{"id":205913,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205915,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205911,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205907,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205909,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205917,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]}]}]
While the below is from our account and it doesn't include that
[{"description":"Load Balancer Data Processed ","id":10771,"keyName":"LOAD_BALANCER_DATA_PROCESSED","units":"GIGABYTE","prices":[{"id":205837,"categories":[{"categoryCode":"load_balancer_data_processed","id":1228,"name":"Load Balancer Data Processed"}]}]},{"capacity":"0","description":"Load Balancer as a Service","id":10043,"keyName":"LOAD_BALANCER_AS_A_SERVICE","prices":[{"id":199445,"categories":[{"categoryCode":"load_balancer_as_a_service","id":1116,"name":"Load Balancer As A Service"}]}]},{"capacity":"0","description":"Load Balancer Bandwidth","id":10051,"keyName":"LOAD_BALANCER_BANDWIDTH","units":"GB","prices":[{"id":199465,"categories":[{"categoryCode":"load_balancer_bandwidth","id":1117,"name":"Load Balancer Bandwidth"}]}]},{"capacity":"0","description":"Load Balancer Uptime","id":10785,"keyName":"LOAD_BALANCER_UPTIME","units":"hour","prices":[{"id":205975,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205981,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205983,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205979,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205977,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]},{"id":205985,"categories":[{"categoryCode":"load_balancer_uptime","id":1119,"name":"Load Balancer Uptime"}]}]}]
I am going to give you another branch in few minutes, please try and let us know..
Fixed in master branch. You can build latest from that. Official binary would be provided soon.
Also datacenter
should be removed from the configuration as the order will infer that from the subnet.
Meanwhile here is the binary for mac/linux
darwin_amd64.zip
linux_amd64.zip
Please re-open if still an issue.
When trying to provision LBaaS in both Dallas 13 and Wdc07 I am getting an error about pricing. I am using IBM Cloud Provider v0.5.0.
Terraform Version
$ terraform -v
Terraform v0.10.7
Affected Resource(s)
Please list the resources as a list, for example:
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Debug Output
https://gist.github.com/greyhoundforty/650bf379f2f5a575e120db307c43c67a
Expected Behavior
4 VSIs provisioned with a LBaaS instance
Actual Behavior
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply