-
Notifications
You must be signed in to change notification settings - Fork 820
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
Unable to start Hyperledger Besu node on Openshift with error: Nat manager failed to configure itself automatically due to the following reason : #6724
Comments
Changing the image version to 23.10.2 I obtain the following error:
|
does |
@garyschulte no, the rpc-service-read-role is a simple Role, not a ClusterRole as this is a security requirement in my company. |
Since it is a test rig, perhaps promote the role to test and let us know if that solves your problem. Since it has gone dormant, I will dust off the k8s namespace PR and see about getting it merged. |
@garyschulte That would be great, I'll try to promote the role and let You know |
We created a ClusterRole and RoleBinding to get the service list, and mounted the relative service account on the pod but nothing changed.
Following the RBAC Configuration:
|
@garyschulte Trying to solve the problem locally (excluding the K8S cluster) I created a whole local network with a docker compose file, but every node of the network is not syncing. Maybe solving this I'll be able to solve the problem in K8S too. Can you try to reproduce this environment and try to understand what is not working? I generated the key pairs with besu operator. One question: what happens if the genesis file provided at key pairs generation time is different from the genesis file provided to the nodes when starting besu? Thank you Docker compose manifest
genesis.json
env file sibling of docker-compose.yaml
|
QBFT requires that the genesis file's extraData contains the encoded node addresses of your initial validator set. The extraData in the genesis you provided is Does this list match your actually deployed validator addresses? Btw, your rpc config contains IBFT instead of QBFT, e.g. Finally, from the k8s side, are you familiar with this tutorial? https://besu.hyperledger.org/private-networks/tutorials/kubernetes |
@siladu Thank you for your suggestions, the list of validator nodes address doesn't match with my actual validator pool addresses. I'll fix it and try again. Regarding the K8S tutorial I've started to familiarize with the tutorial deploying on a Kubernetes cluster one single node with nat-method NONE in a test environment. I will read carefully the article you posted to find the best way to deploy nodes. |
I'm trying to deploy a Hyperledger Besu node from inside an Openshift / Kubernetes cluster. For test purposes I'm deploying It as a ReplicaSet, but i will switch to StatefulSet when it will be up, running and synchronizing with other peers (which are running outside the cluster).
When the POD starts prints the following:
If I switch to nat-method NONE how can I determine the enode address advertised?
Thank you in advance
My K8S manifests:
RBAC
Service
Genesis config map
Config toml config map
Deployment
The text was updated successfully, but these errors were encountered: