# Harness: CI git clone calls are failing for specific arm builds

- Impact (vendor’s label): minor
- Status: postmortem
- Started: 2026-07-17 10:30 UTC · Resolved: 2026-07-17 14:16 UTC · Duration: 3.8 h
- Updates: 6 · Affected components: Continuous Integration Enterprise(CIE) - Self Hosted Runners, Prod 1 - Continuous Integration Enterprise(CIE) - Self Hosted Runners
- [Vendor status page: https://stspg.io/pljx3l92jxgx](https://stspg.io/pljx3l92jxgx)
- [Company: Harness](https://rewindex.com/company/harness.md)

## Timeline of updates

- **investigating** 2026-07-17 10:30 UTC: We are currently investigating this issue.
- **identified** 2026-07-17 13:12 UTC: The issue has been identified and a fix is being implemented.
- **monitoring** 2026-07-17 13:19 UTC: A fix has been implemented and we are monitoring the results.
- **monitoring** 2026-07-17 13:19 UTC: We are continuing to monitor for any further issues.
- **resolved** 2026-07-17 14:16 UTC: This incident has been resolved.
- **postmortem** 2026-07-22 17:25 UTC: \# Summary Between June 19 and July 17, 2026, the built-in Git Clone step — and any pipeline step using the drone-git clone plugin — failed on ARM64 Kubernetes build infrastructure with the error exec /usr/local/bin/clone: exec format error. AMD64 \\(Intel/AMD\\) builds, Windows builds, and the VM containerless binary path were not affected. The root cause was a defect in our internal image publishing process that caused ARM64-tagged drone-git images to actually contain AMD64 binaries. We identified and mitigated the issue the same day it was reported by reverting the drone-git image to the last known-good version. No customer action or configuration change was required. \# Root Cause On June 19, 2026, a security remediation restructured how the drone-git image is built. AMD64 builds were updated correctly, but the ARM64 build pipeline didn't build ARM64 files directly — it adapted the AMD64 build file via text substitution and compiled it on ARM64 infrastructure. The June 19 change altered the AMD64 file so that substitution silently no-op'd instead of failing, so the pipeline published an image tagged ARM64 whose Git Clone and Git LFS binaries were still compiled for AMD64. \# Impact \* Affected: The built-in Git Clone step, and any pipeline step using the drone-git clone plugin, running on ARM64 Kubernetes build infrastructure, across all accounts, between July 6 and July 17, 2026. \* Symptom: Builds failed at the Git Clone step with exec /usr/local/bin/clone: exec format error. \* Not affected: AMD64 \\(Intel/AMD\\) Kubernetes and VM builds, Windows builds, the VM containerless execution path, and our hardened image variant. \# Mitigation We reverted the drone-git image version used across all affected services to the last known-good release. This fully resolved the ARM64 execution failures; no customer configuration changes were required. \# Next Steps To prevent such issues from happening again. \* Rebuild the ARM64 image publishing pipeline to build our dedicated ARM64 build files directly, rather than adapting the AMD64 build files. \* Enhance automated post-publish validation to every image release: verify binary architecture matches the image tag, and run a functional smoke test before an image is considered releasable. \* Expand automated test coverage to include ARM64 Kubernetes build scenarios. \* Remove the affected intermediate image versions from circulation once the corrected release is validated.


---
Canonical: https://rewindex.com/company/harness/incidents/pv1ntnb805xw · Markdown: https://rewindex.com/company/harness/incidents/pv1ntnb805xw.md · JSON: https://rewindex.com/api/v1/companies/harness/incidents/pv1ntnb805xw · Generated 2026-10-20T01:31:57.299Z