-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
v3 api is not available when etcd uses config file #12093
Comments
@DenisRazinkin please try enabling enable-grpc-gateway in the config file i.e. |
Currently, the grpc gateway is enabled by default when run the etcd server using command line configuration. However, when provide config through config file, the grpc gateway is disabled by default. We should either use the same approach or at least document this. related #etcd-io#12093
Currently, the grpc gateway is enabled by default when run the etcd server using command line configuration. However, when provide config through config file, the grpc gateway is disabled by default. We should either use the same approach or at least document this. related #etcd-io#12093
Closing as fixed. Thanks! |
Say folks, would you add this parameter to the docs please? I spent quite a few hours wondering what was missing until CyberDem0n pointed me to this issue. See patroni/patroni#1939 While you're at it, maybe a way to search the docs? |
Updating changelog #13034 and will add in doc appropriately in the etcd.io repo https://github.com/etcd-io/website |
This patch fixes a problem with OpenStack tooz's etcd3gw driver when it attempts to communicate with the etcd service. The tooz driver uses etcd's grpc gateway functionality, but starting with etcd v3.3 the grpc gateway is not enabled by default (for wallaby, centos-8 includes etcd v3.2, but centos-9 incudes v3.4). Per [1], the fix involves adding a small config change to the etcd config file. [1] etcd-io/etcd#12093 (comment) Normally this would be handled by puppet-etcd, but that puppet module is *not* an opendev project, and is quite out of date. It would take a lot of work to update puppet-etcd, with little benefit beyond supporting [1]. The solution implemented here is to enhance the puppet_config tasks to add the missing config after puppet-etcd finishes. The long term solution is to replace puppet-etcd with a tripleo-ansible role, but that's a larger effort. This patch also removes the container_puppet_tasks that were originally intended so tripleo could inject key/value pairs into etcd. However, that functionality was never utilized, and is currently broken due to it mounting etcd's database directory in read-only mode. The container_puppet_tasks need to be removed in order for the new puppet_config tasks to work correctly. Resolves: rhbz#2097058 Change-Id: I3ed29a14298f4df94b8a5520615bfa85cd291346
* Update tripleo-heat-templates from branch 'master' to 26ecf8c3b12c39328a9fb90cf3cd72c216b1ad20 - Merge "etcd: fix service config to work with latest versions" - etcd: fix service config to work with latest versions This patch fixes a problem with OpenStack tooz's etcd3gw driver when it attempts to communicate with the etcd service. The tooz driver uses etcd's grpc gateway functionality, but starting with etcd v3.3 the grpc gateway is not enabled by default (for wallaby, centos-8 includes etcd v3.2, but centos-9 incudes v3.4). Per [1], the fix involves adding a small config change to the etcd config file. [1] etcd-io/etcd#12093 (comment) Normally this would be handled by puppet-etcd, but that puppet module is *not* an opendev project, and is quite out of date. It would take a lot of work to update puppet-etcd, with little benefit beyond supporting [1]. The solution implemented here is to enhance the puppet_config tasks to add the missing config after puppet-etcd finishes. The long term solution is to replace puppet-etcd with a tripleo-ansible role, but that's a larger effort. This patch also removes the container_puppet_tasks that were originally intended so tripleo could inject key/value pairs into etcd. However, that functionality was never utilized, and is currently broken due to it mounting etcd's database directory in read-only mode. The container_puppet_tasks need to be removed in order for the new puppet_config tasks to work correctly. Resolves: rhbz#2097058 Change-Id: I3ed29a14298f4df94b8a5520615bfa85cd291346
This patch fixes a problem with OpenStack tooz's etcd3gw driver when it attempts to communicate with the etcd service. The tooz driver uses etcd's grpc gateway functionality, but starting with etcd v3.3 the grpc gateway is not enabled by default (for wallaby, centos-8 includes etcd v3.2, but centos-9 incudes v3.4). Per [1], the fix involves adding a small config change to the etcd config file. [1] etcd-io/etcd#12093 (comment) Normally this would be handled by puppet-etcd, but that puppet module is *not* an opendev project, and is quite out of date. It would take a lot of work to update puppet-etcd, with little benefit beyond supporting [1]. The solution implemented here is to enhance the puppet_config tasks to add the missing config after puppet-etcd finishes. The long term solution is to replace puppet-etcd with a tripleo-ansible role, but that's a larger effort. This patch also removes the container_puppet_tasks that were originally intended so tripleo could inject key/value pairs into etcd. However, that functionality was never utilized, and is currently broken due to it mounting etcd's database directory in read-only mode. The container_puppet_tasks need to be removed in order for the new puppet_config tasks to work correctly. Resolves: rhbz#2097058 Change-Id: I3ed29a14298f4df94b8a5520615bfa85cd291346 (cherry picked from commit 796f6a5)
This is still missing in the docs @spzala - can we please add it to https://github.com/etcd-io/website? |
-bash-4.4# etcd --version
etcd Version: 3.4.9
Git SHA: 54ba958
Go Version: go1.12.17
Go OS/Arch: linux/amd64
There is no problem with v3 api when I start etcd with command line
-bash-4.4# etcd --data-dir=/tmp/node1 --name node1 --listen-peer-urls=http://127.0.0.1:2380 --listen-client-urls=http://127.0.0.1:2379 --initial-advertise-peer-urls=http://127.0.0.1:2380 --advertise-client-urls=http://127.0.0.1:2379
When I use config file with same parameters there is 404 error.
Start etcd with:
-bash-4.4# etcd --config-file /tmp/node1/etcd.conf
Send curl http request, got 404
The text was updated successfully, but these errors were encountered: