Open gautamgadipudi-hpe opened 2 weeks ago
Hey @gautamgadipudi-hpe,
Thank you for reporting this issue. Is there a script used for joining/creating the cluster?
I believe the issue might be related to dqlite not having enough time to initialize and update the info.yaml
file which is used in assembling the list of cluster members when joining. We'll try to see if this is reproducable.
Using ansible scripts, we use launch configuration files with tokens to form the cluster. We start microk8s on 1 node at a time and wait for that to stabilize by checking microk8s status --wait-ready
and microk8s kubectl wait --for=condition=Ready node --all
output.
Please let us know if there is any other recommendations.
Build details
We are using microk8s FIPS package (version 1.28.13). This snap package is created manually by cloning the
1.28
branch of microk8s and cherry-picking the FIPS commit - https://github.com/canonical/microk8s/commit/a55910917fd43aff113abf2f7cb2b5844389c41b. Then building the snap package using below commands:Summary
We are trying to setup a 3 node cluster (1 controller and 2 master nodes)
The controller node and the first master node are up, but the second master node failed to join the cluster.
Below are the
microk8s.daemon-cluster-agent
errors on the 3rd node when it tried to join the cluster.What Should Happen Instead?
Reproduction Steps
This seems like an intermittent issue. We were able the cluster up and running in the next iteration.
Introspection Report
inspection-report-20240930_191036.tar.gz inspection-report-20240930_191723.tar.gz inspection-report-20240930_191728.tar.gz