events: an e2e test — an emitted event reaches the audit trail over the mesh's broker #2
@@ -1403,7 +1403,9 @@ test("a service is reached by a name under the machine it runs on", {
|
|||||||
`journal:\n${(await on(machine, `journalctl -u dnsmasq -n 25 --no-pager`)).out}\n` +
|
`journal:\n${(await on(machine, `journalctl -u dnsmasq -n 25 --no-pager`)).out}\n` +
|
||||||
`its config:\n${(await on(machine, `cat /etc/dnsmasq.conf`)).out}\n` +
|
`its config:\n${(await on(machine, `cat /etc/dnsmasq.conf`)).out}\n` +
|
||||||
`what the mesh wrote:\n${(await on(machine, `cat /etc/mesh-resolver/nodes.conf`)).out}\n` +
|
`what the mesh wrote:\n${(await on(machine, `cat /etc/mesh-resolver/nodes.conf`)).out}\n` +
|
||||||
`resolv.conf:\n${(await on(machine, `cat /etc/resolv.conf`)).out}`);
|
`resolv.conf:\n${(await on(machine, `cat /etc/resolv.conf`)).out}\n` +
|
||||||
|
`what holds a loopback address:\n` +
|
||||||
|
`${(await on(machine, `ss -lntup | grep 127.0.0 || echo none`)).out}`);
|
||||||
}
|
}
|
||||||
|
|
||||||
// Through the machine's own resolver, by the path an application actually takes: nsswitch, then
|
// Through the machine's own resolver, by the path an application actually takes: nsswitch, then
|
||||||
|
|||||||
Reference in New Issue
Block a user