Impact

An unknown number of groups experienced issues cloning repositories via Egress IP and ZTNA. The issue started on UTC-5 24-10-07 15:34 and was proactively discovered 1.2 hours (TTD) later by one of our engagement managers who reported through our help desk [1] that they encountered an error stating: Could not find the repository or resolve the host. The problem was resolved in 2.9 days (TTF), resulting in a total impact of 3 days (TTR) [2].

Cause

Cloudflare Warp was installed with different versions at the container and host levels. When Cloudflare updated Warp, the version mismatch caused an incompatibility, leading to issues during repository cloning.

Solution

Cloudflare Warp was updated at the container level using an override to fix a more recent version. Additionally, adjustments were made to the cloning logic to accommodate the changes introduced in this version [3].

Conclusion

The issue stemmed from needing the dependency in two environments with different installation methods, leading to a version mismatch. We´re working on a solution to ensure both environments always use identical versions to prevent future disparities. THIRD_PARTY_CHANGE < INCOMPLETE_PERSPECTIVE