Skip to content
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

scale nodepools Kubernetes1.30 & TF Provider 2.0.2 #421

Open
cccdemon opened this issue Jan 24, 2025 · 15 comments
Open

scale nodepools Kubernetes1.30 & TF Provider 2.0.2 #421

cccdemon opened this issue Jan 24, 2025 · 15 comments

Comments

@cccdemon
Copy link

cccdemon commented Jan 24, 2025

Terraform update nodepool scale from 3 to 5 nodes in a nodepool leads to an error.

Error: update k8s (HIDDEN) resource - error: Status code: 400. Error: {'type': 'HTTPError', 'status_code': 400, 'message': "(400, 'Scale in/out (Horizontal Pool Scaling) is not allowed to be combined with updating Pool Worker Resource (Vertical Pool Scaling). Please, update Pool resource; then scale out/in your Pool')"}. Request UUID: 7abe6061-2e8f-44fc-a947-2a15c5e16680.

Even from the Panel i cant add more nodes.

@cccdemon cccdemon changed the title scale nodepools 2.0.2 scale nodepools Kubernetes1.30 & TF Provider 2.0.2 Jan 24, 2025
@cccdemon
Copy link
Author

tested via Panel to add a new nodePool.
Does not work either

@nvthongswansea
Copy link
Member

@cccdemon Hi, does adding nodepool work for you yet?

@cccdemon
Copy link
Author

Will test it, wait a sec

@cccdemon
Copy link
Author

nope, not working :(

@nvthongswansea
Copy link
Member

nvthongswansea commented Jan 24, 2025

@cccdemon This is a validation error, the request is not recorded in our system (because we don't record request with code 400). Could you open a ticket in gridscale which includes your cluster UUID, please?

@cccdemon
Copy link
Author

already done.

@cccdemon
Copy link
Author

New Request UUID: d6385fb8-3cc9-44dc-a583-a1c6b0576746

@cccdemon
Copy link
Author

2025-01-24T11:18:41.354+0100 [DEBUG] provider.terraform-provider-gridscale_v2.0.2: time="2025-01-24T11:18:41+01:00" level=debug msg="Request headers: map[Content-Type:[application/json] User-Agent:[terraform-provider-gridscale/2.0.2-aa44bb8f8b5d7a0e528dd305ceaeb18b61ccb4bf-darwin] X-Auth-Token:[e5bd2XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX] X-Auth-Userid:[3c906XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX]]"
2025-01-24T11:18:41.572+0100 [DEBUG] provider.terraform-provider-gridscale_v2.0.2: time="2025-01-24T11:18:41+01:00" level=debug msg="Status code: 200. Request UUID: c8b52f24-6658-4348-a84e-795c9cf5b00c. Headers: map[Access-Control-Allow-Credentials:[true] Access-Control-Allow-Headers:[Origin, X-Requested-With, Content-Type, Accept, X-Auth-UserId, X-Auth-Token, X-Exec-Time, X-API-Version, X-Api-Client, X-API-Identity, X-Auth-ContractId, X-Auth-ProjectId, X-Auth-PartnerId] Access-Control-Allow-Methods:[GET, POST, PUT, PATCH, DELETE, OPTIONS] Access-Control-Allow-Origin:[*] Access-Control-Expose-Headers:[X-Exec-Time, X-API-Version, X-Request-Id, X-API-Identity] Cache-Control:[no-cache] Content-Length:[123] Content-Type:[application/json] Date:[Fri, 24 Jan 2025 10:18:41 GMT] Etag:[\"W/2c64a3ac0282c5f326e5f14e797b97ebfaf50c73\"] Strict-Transport-Security:[max-age=31536000] X-Api-Identity:[2] X-Request-Id:[c8b52f24-6658-4348-a84e-795c9cf5b00c] X-Time-Provisioning:[0.159917]]"
2025-01-24T11:18:41.572+0100 [DEBUG] provider.terraform-provider-gridscale_v2.0.2: time="2025-01-24T11:18:41+01:00" level=debug msg="Response body: {\"51eeb3b8-eb66-459e-a771-80668488ae88\": {\"message\": \"Failure\", \"status\": \"failed\", \"create_time\": \"2025-01-24T10:18:31Z\"}}"
2025-01-24T11:18:41.573+0100 [ERROR] provider.terraform-provider-gridscale_v2.0.2: Response contains error diagnostic: tf_req_id=b3ba06cb-4968-88d8-b2e8-1d8c1accd604 tf_rpc=ApplyResourceChange tf_provider_addr=provider diagnostic_detail="" diagnostic_severity=ERROR diagnostic_summary="update k8s (c4e12d4b-ab31-48a5-996b-c2cda955ec78) resource - error: request 51eeb3b8-eb66-459e-a771-80668488ae88 failed with error Failure" tf_proto_version=5.7 tf_resource_type=gridscale_k8s @caller=github.com/hashicorp/[email protected]/tfprotov5/internal/diag/diagnostics.go:58 @module=sdk.proto timestamp="2025-01-24T11:18:41.573+0100"
2025-01-24T11:18:41.576+0100 [DEBUG] State storage *remote.State declined to persist a state snapshot
2025-01-24T11:18:41.576+0100 [ERROR] vertex "module.k8[\"general\"].gridscale_k8s.kubernetes" error: update k8s (c4e12d4b-ab31-48a5-996b-c2cda955ec78) resource - error: request 51eeb3b8-eb66-459e-a771-80668488ae88 failed with error Failure
2025-01-24T11:18:41.578+0100 [DEBUG] states/remote: state read serial is: 13; serial is: 13
2025-01-24T11:18:41.578+0100 [DEBUG] states/remote: state read lineage is: e4ef83f8-f526-fb9c-fb48-8f052c767790; lineage is: e4ef83f8-f526-fb9c-fb48-8f052c767790``` 

@nvthongswansea
Copy link
Member

@cccdemon before doing any scaling/update, could you please add the parameter rocket_storage = 0 in all of your pool named logging. Then do terraform apply, and then try to do your change after that.

@cccdemon
Copy link
Author

Same behavior unfortunatly
Request UUID: 75c053db-2c50-4979-9458-c4351fa3f72a

│ Error: update k8s (HIDDEN) resource - error: request 75c053db-2c50-4979-9458-c4351fa3f72a failed with error Failure

│ with module.k8["general"].gridscale_k8s.kubernetes,
│ on modules/k8/main.tf line 1, in resource "gridscale_k8s" "kubernetes":
│ 1: resource "gridscale_k8s" "kubernetes" {

@cccdemon
Copy link
Author

added the rocket_storage = 0 to the nodepool

after that, i tried to scale - not working
Request UUID fb6dcd9a-a5ef-4bde-8d79-9c72a813b64d

@nvthongswansea
Copy link
Member

@cccdemon Update: I am working on a fix in terraform. I will inform you when the fix is available.

@cccdemon
Copy link
Author

@nvthongswansea thank you, please be aware that the change is also not possible via Panel!

@cccdemon
Copy link
Author

cccdemon commented Jan 24, 2025

@nvthongswansea mybe this is related:
kubectl top nodes results in an:
node-default-1 <unknown> <unknown> <unknown> <unknown>

@nvthongswansea
Copy link
Member

@cccdemon Regarding the failed request when you do the change via gridscale panel, my other teammate already contacted you about the firewall thing. Regarding terraform, I've made a new release v2.0.3, please upgrade and follow the last line in known-issues before applying your changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants