You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test(e2e): check that a sandbox's SSH host key survives a gateway restart #5652
PR #5442 ports e2e/rust/tests/ssh_host_identity.rs to the conformance suite and deletes it. The legacy test also checked that a sandbox's SSH host key survives a gateway restart. The conformance port can't, because testkit can't restart the gateway yet. That half of the test is dropped until the gateway-control family exists (#5281).
The legacy check ran only when the harness managed the gateway (ManagedGateway::from_env()); against an existing gateway it was skipped.
What to port
With a sandbox that has a pinned known_hosts entry from sandbox ssh-config:
Stop and start the gateway, then wait for it to be healthy.
Wait for the sandbox to be Ready and for sandbox exec to work.
The fingerprint in sandbox get is unchanged.
A plain ssh with the pinned known_hosts and StrictHostKeyChecking=yes still connects.
The stop/start and recreate checks are already covered in tests/suites/conformance/src/ssh.rs (ssh_host_identity_stable_across_stop_start_and_new_on_recreate). The new test can reuse its ssh-config and pinned-ssh steps.
Definition of done
A gateway-control test checks that the SSH host key survives a gateway restart.
Activity