[Bug] [v21.11.0] Disable Flag gateway-failover not working correctly #173
Comments
|
It's not a bug. The name of the cluster MUST be the LAST parameter of the command line
but safescaled SEES this command (it stops reading after the cluster name):
if you want to take into account all parameters you should write (notice the position of the cluster's name):
future releases of SafeScale will issue a warning about this (saying that running the command without modifications such and such parameters are IGNORED) |
|
I was not aware that the order is significant and I recreated the command incorrectly when I created the ticket. However, the suggested command was the one already executed which still suffer the mentioned issue.
INFO [2022-03-29 14:44:30.227][info][ 9724] Checking configuration |
|
If the problem is the log message "We have a primary gateway etc. etc." it could have been a Warning message too, we just wanted to make sure this kind of issue was displayed, it doesn't stop the cluster creation process. But, if the problem is the "stuck here", and by that you mean "stuck there forever", then yes, it must NOT happen, and it's some kind of deadlock; if you confirm it's the latter we will retag the issue as a "bug" and will look into it |
|
Yes it's the later, indeed probably some kind of deadlock, it stays like this forever and even other basic commands like cluster list won't work anymore once it reach this state |
|
Please, try again, this time with the following command (forcing a cidr):
and let us know if it works. |
|
It seems commit 384f482 introduced a severe regression, develop branch has several deadlocks right now. This will be fixed next week. In order to build release/v21.11 binaries: and the binaries should be in the ./exported directory |
|
Forcing the CIDR sadly didn't improve the outcome, with a deadlock still being present. Thanks for the recommendation, but I also need the corrections from #149. It works without this flag but I still encounter timeouts issues on the cluster creation process. I will try without it and increasing the timeouts for the time being. Thank you a lot for your help |
|
Corrections from #149 are already on release/v21.11; recreating the binaries with branch release/v21.11 works with the following command (tested yesterday), and uses the right templates too: |
|
In the end I managed to have the cluster creation successful trying both the release and the latest develop after trying various timeout modification, and both seems to be working. Thanks again |
|
Fixed in develop. Will be included in upcoming release v21.11.1. |
version: v21.11.0
When trying to create a cluster with the following command:
safescale cluster create callisto --complexity=Normal --flavor=K8S --gw-sizing="template=d2-2" --master-sizing="template=b2-7" --node-sizing="template=b2-30" --disable gateway-failoverThe creation fails with the following message:
ERROR [2022-03-29 11:36:47.170][error][ 4006] We have a primary gateway with name gw-callisto and id 19bac927-a53c-4391-8844-c5af6a09629b and a secondary gateway with name gw-callisto and id 19bac927-a53c-4391-8844-c5af6a09629bThe relevant logs section:
safescale.log
The text was updated successfully, but these errors were encountered: