I'm still seeing this on master. I've attached the deployment output and I can see that I do have the keepalive fix on the undercloud:
[ssh_connection] ssh_args = -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o ControlMaster=auto -o ControlPersist=30m -o ServerAliveInterval=5 -o ServerAliveCountMax=5
This is doing a fairly basic deployment using the OVB multinic templates: https://github.com/cybertron/openstack-virtual-baremetal/tree/master/overcloud-templates/network-templates-v2
Deploy command is this: openstack overcloud deploy --templates --libvirt-type qemu -e /usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml -e /home/centos/openstack-virtual-baremetal/overcloud-templates/network-templates-v2/network-isolation-absolute.yaml -e /home/centos/openstack-virtual-baremetal/overcloud-templates/network-templates-v2/network-environment.yaml
I'm still seeing this on master. I've attached the deployment output and I can see that I do have the keepalive fix on the undercloud:
[ssh_connection] ile=/dev/ null -o StrictHostKeyCh ecking= no -o ControlMaster=auto -o ControlPersist=30m -o ServerAliveInte rval=5 -o ServerAliveCoun tMax=5
ssh_args = -o UserKnownHostsF
This is doing a fairly basic deployment using the OVB multinic templates: https:/ /github. com/cybertron/ openstack- virtual- baremetal/ tree/master/ overcloud- templates/ network- templates- v2
Deploy command is this: openstack overcloud deploy --templates --libvirt-type qemu -e /usr/share/ openstack- tripleo- heat-templates/ environments/ disable- telemetry. yaml -e /home/centos/ openstack- virtual- baremetal/ overcloud- templates/ network- templates- v2/network- isolation- absolute. yaml -e /home/centos/ openstack- virtual- baremetal/ overcloud- templates/ network- templates- v2/network- environment. yaml