markap14 commented on PR #11231: URL: https://github.com/apache/nifi/pull/11231#issuecomment-4422477082
[claude-opus-4.7] CI failure on \`ubuntu-24.04 Java 21\` is a pre-existing system-test flake, not related to this PR. **Failing job:** [system-tests / ubuntu-24.04 Java 21](https://github.com/apache/nifi/actions/runs/25678529070/job/75383499711) **Tests that errored (8 total):** - \`ClusteredConnectorIT.testBundleResolutionRequireExactBundle\` - \`ClusteredConnectorIT.testBundleResolutionResolveNewestBundle\` - \`ClusteredConnectorIT.testCreateConfigureRestart\` - \`ClusteredConnectorIT.testBundleResolutionResolveBundle\` - \`ClusteredConnectorIT.testSecretReferences\` - \`ClusteredConnectorIT.testDeleteConnectorNoDataQueued\` - \`ClusteredConnectorDrainIT.testDrainWithNodeCompletingAtDifferentTimes\` - \`ClusteredConnectorDrainIT.testCancelDrainWithOneNodeAlreadyComplete\` **Error (same on all 8):** \`\`\` org.apache.nifi.toolkit.client.NiFiClientException: Error applying connector update: Node localhost:5672 is unable to fulfill this request due to: This node is disconnected from its configured cluster. The requested change will only be allowed if the flag to acknowledge the disconnected node is set. Caused by: jakarta.ws.rs.ClientErrorException: HTTP 409 Conflict at org.apache.nifi.toolkit.client.impl.AbstractJerseyClient.executeAction(AbstractJerseyClient.java:96) at org.apache.nifi.toolkit.client.impl.JerseyConnectorClient.applyUpdate(JerseyConnectorClient.java:422) \`\`\` Each test fails in <1s on the very first API call to node-2; the troubleshooting log shows the cluster coordinator believes both nodes are CONNECTED while node-2 itself answers 409 \"disconnected\". Tests share a cached two-node NiFi instance and the inconsistency carries from a prior test in the same run. **Why this is a pre-existing flake, not caused by the PR:** 1. The exact same eight tests failed on \`main\` on May 5 in run [25366699710 / ubuntu-24.04 Java 21](https://github.com/apache/nifi/actions/runs/25366699710/job/74379286719) with the same elapsed times and the same \`Node localhost:5672 ... disconnected from its configured cluster\` error. 2. \`ubuntu-24.04 Java 25\` (same module, same shard, different JDK) passed in this run, so it isn't a deterministic break. 3. The failures are coordinator/node cluster state desync, not anything in the connector sync-mode path this PR touches. **Plan:** Once the parent \`system-tests\` run finishes, I'll rerun the failed shard. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
