chore(cloudflared): target 2026.7.3 - #29
Merged
Merged
Conversation
Applied to cloudflared_vm and verified: the tunnel registered four QUIC connections (cgk02, sin13, sin11, cgk07) after the handler restart, and cloudflared's own precheck passed DNS, UDP and TCP against both regions. The upgrade had been blocked rather than untried. The guest's root was 100% full, so ansible could not write its module payload to /tmp and every run ended UNREACHABLE at Gathering Facts - see the storage reclaim playbook added alongside this.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
cloudflared_version_targetfrom2026.2.0to2026.7.3.Already applied and verified on
cloudflared_vm— this commits the changethat was made to reach it:
Tunnel health after the handler restart, not just
systemctl is-active:precheck complete hard_fail=false— DNS, QUIC/UDP and HTTP/2/TCP allpassagainst both
region1andregion2cgk02,sin13,sin11,cgk07The
ERR Connection terminated/no more connections active and exitinglinesin the journal are the old process shutting down for the restart — every
registration is timestamped after them.
Why this had not landed
The upgrade was blocked, not untried. The guest's root was 100% full, so Ansible
could not write its module payload to
/tmpand every run endedUNREACHABLEatGathering Facts. #28 adds the reclaim playbook that clears that, and this guestis its worked example.
Pre-existing and unrelated, noted here rather than fixed: cloudflared logs a
ping_group_rangewarning and disables its ICMP proxy. Only matters if ICMP isproxied through the tunnel.