docs(2.9): H4 route pinning applied and verified; fix the stub= pattern - #574
Merged
Conversation
ip route get 192.168.1.128 now returns dev enp2s0 src 192.168.1.160, where yesterday it returned dev enp1s0 src 192.168.1.156. Default routes are enp2s0 at metric 100 and enp1s0 at 200. Applied via netplan try, which offered the 120-second prompt. The check that mattered more than the routes: grep -c nameserver /run/systemd/resolve/resolv.conf still returns 3. netplan try re-applies both links, which is exactly the operation that produced 4.12's count of six, so a clean route change that silently reopened the resolver bug next door was the realistic failure. use-dns: false on both links held, and all five nodes stayed Ready on a host that is an etcd voter. Also fixes the stub= check in h4-disable-dnsmasq.yml. ss renders the resolved stub with its interface suffix, 127.0.0.53%lo:53, so the pattern 127\\.0\\.0\\.53:53 never matched and the play printed stub=0 beside a success message saying the stub was present and expected. A check whose pattern misses reality, reported next to prose implying it did not. Corrected pattern tested against the real ss rendering.
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
ip route get 192.168.1.128 now returns dev enp2s0 src 192.168.1.160, where yesterday it returned dev enp1s0 src 192.168.1.156. Default routes are enp2s0 at metric 100 and enp1s0 at 200. Applied via netplan try, which offered the 120-second prompt.
The check that mattered more than the routes: grep -c nameserver /run/systemd/resolve/resolv.conf still returns 3. netplan try re-applies both links, which is exactly the operation that produced 4.12's count of six, so a clean route change that silently reopened the resolver bug next door was the realistic failure. use-dns: false on both links held, and all five nodes stayed Ready on a host that is an etcd voter.
Also fixes the stub= check in h4-disable-dnsmasq.yml. ss renders the resolved stub with its interface suffix, 127.0.0.53%lo:53, so the pattern 127\.0\.0\.53:53 never matched and the play printed stub=0 beside a success message saying the stub was present and expected. A check whose pattern misses reality, reported next to prose implying it did not. Corrected pattern tested against the real ss rendering.