Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The error AttributeError("'int' object has no attribute 'get'") means Patroni’s member-discovery lookup raised an exception; it does not, by itself, identify whether the cause is an etcd API response, version behavior, address, or configuration mismatch. An Ubuntu 24.04 report attributes one occurrence to etcd 3.4.30, but that cause is not independently confirmed. Start by verifying the running versions and inspecting the exact endpoint response Patroni receives before changing the DCS backend or upgrading a live cluster.
What the error tells you—and what it does not
Patroni’s source has a member-discovery method that calls a member lookup for candidate base URLs. If that lookup raises an exception, it logs Failed to get list of machines from %s%s: %r. So the message identifies a failure during discovery; it does not reveal which response or compatibility condition caused it. See Patroni’s etcd DCS source.
A Patroni issue opened June 5, 2026 reports this exact exception with Patroni 4.1.3, Python 3.12, etcd 3.4.36, and PostgreSQL 18. The reporter used an etcd3: configuration without an etcd: section and saw:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsFailed to get list of machines from http://10.245.7.12:2379/v3: AttributeError("'int' object has no attribute 'get'")
#1 Best Overall
This is a user-reported environment and log, not a maintainer-confirmed explanation or a universal version compatibility result. The reporter suspected that member discovery was reaching logic inherited from Patroni’s etcd.py path. The issue establishes the symptom in that setup, not the underlying cause. Read the Patroni issue report.
Why Ubuntu 24.04’s etcd version is only a lead
An October 1, 2026 DEV Community article reports that Ubuntu 24.04’s etcd 3.4.30 returned HTTP 404 for POST /v3/cluster/member/list in the author’s test, while etcd 3.6.15 returned a member list. The author says upgrading resolved the problem in that setup and recommends etcd 3.5 or newer. The article could not be independently checked, so treat its package-specific cause and upgrade result as that author’s report, not a guarantee for every Ubuntu installation.
The separate Patroni issue reports the same exception with etcd 3.4.36. That difference is another reason not to infer the cause from the Ubuntu release alone. Verify the package and binaries actually running on your hosts, then inspect the request and response at the endpoint Patroni contacts.
Diagnose the endpoint Patroni actually uses
-
Record the installed versions and configuration
On the Patroni host and each etcd member, record the exact Patroni, etcd, and Python versions, the configured DCS block, and the client endpoint addresses. Confirm whether the running etcd binaries match the Ubuntu package version; do not assume that the distribution release identifies what is running.
-
Capture the member-list request and response
From the Patroni host, inspect the configured client endpoint and capture the HTTP status, response body, and any proxy or TLS behavior. The Ubuntu article describes testing
POST /v3/cluster/member/listwith an empty JSON body. Confirm that this endpoint and request are appropriate for your exact etcd and Patroni versions before using it as a diagnostic test; it is not established here as a universal test command.A general etcd health check is not a substitute for this inspection: passing a health check does not establish that the member-discovery request Patroni needs succeeds or returns usable data.
-
Compare the response with the configured DCS
Check that Patroni is pointed at the intended etcd client addresses and that the observed request path and returned data make sense for the configured backend. The issue report shows that this exception can occur with
etcd3:alone. Do not add anetcd:block or switch to a legacy backend solely because the log mentions machine discovery.Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Use version documentation to choose a test
If the response shows a missing endpoint or an incompatible response, consult the official documentation for the exact Patroni and etcd releases, then reproduce the issue in a controlled environment. The report recommending etcd 3.5 or newer is not independently verified here and should not replace a compatibility check for your deployment.
Decide whether an etcd upgrade is appropriate
Compare the observed endpoint response, your exact Patroni and etcd versions, their documented compatibility, and the result of a controlled test. An upgrade is a plausible path only when those checks support it; the reported success with etcd 3.6.15 applies to the article author’s test, not every cluster.
For an existing etcd cluster, use etcd’s official upgrade and backup guidance for the exact starting and target releases before changing binaries. Do not wipe or replace data directories as a troubleshooting shortcut. The Ubuntu article’s broader upgrade instructions have not been independently validated here. A legacy v2 backend is not an automatic workaround: verify that it is supported for the precise Patroni and etcd versions and deployment before changing backend configuration.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →
