Jarrod Johnson 6eb4bf28e5 Another iteration to try to have IP adaptive syncfiles ... It is likely that a client connects from fe80::, which is explicitly omitted from ssh principals. This time, have the client provide all currently set IP addresses and the server will make a determination. There remains the possibility it misconfigures a nic and tries to use that, inducing failure. One strategy would be to filter the addresses and only provide from the 'current' interface. Another is to just take the hit as the node is likely going to suffer a lot from such a misconfiguration anyway.		2022-10-05 12:23:47 -04:00
..
common
coreos
debian
el7
el7-diskless
el8	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
el8-diskless	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
el9-diskless	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
esxi7
genesis	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
rhvh4
suse15	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
suse15-diskless
ubuntu20.04	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
ubuntu20.04-diskless
ubuntu22.04	Another iteration to try to have IP adaptive syncfiles	2022-10-05 12:23:47 -04:00
utils
buildrpm
confluent_osdeploy.spec.tmpl