Closed shng4you closed 1 year ago
I realized that my account balance on Testnet was draining very fast, even though I only had a single very cheap VM deployment. As you can see in this screenshot there are zero active kubernetes deployments on my profile.
Then under contracts I could see that even though I had zero kubernetes deployments, there were two active contracts still existing.
This is not supposed to happen right? When I delete a deployment I would assume that it should also delete all corresponding contracts. There is no point in having contracts without deployments.
@jakubprogramming Hi, can you provide me your twin ID and network please?
Yes of course
twin ID: 488 Nework: testnet
There is still a deployment which is active:
{
"resourcesUsed": {
"cru": "1",
"hru": "0",
"mru": "536870912",
"sru": "16630415360"
},
"numberOfPublicIPs": 0,
"contractID": "13537"
}
Yes I know. That is not the problem. I have explained the problem above. The exisiting deployment is fine.
@DylanVerstraete do we know what's happening? is it possibly related to discounts on the TFT balance?
@jakubprogramming is this resolved now?
For me personally it was resolved as soon as I deleted the active contracts. I don't know if it could potentially still happen to others. IMO every time an active deployment is deleted its corresponding contract should as well. Thats what usually happens too. In my case it did not and the contract had to be deleted manually.
Will close, please reopen if it happens again
Since Monday I have been billed more than 20 TFT, but I should only have been billed about 7,5 TFT. I don't know for how long I am overpaying. I just noticed that my account balance is draining very fast. I've had many more deployments (and contracts) in the past. Normally when I deleted a deployment billing was stopped. I did not have to delete the contract seperately. This is not supposed to happen right? When I delete a deployment I would assume that it should also delete all corresponding contracts. There is no point in having contracts without deployments.