Looking into this test failure:
1..4
ok 1 proxy is registered
ok 2 enable lifecycle environment for proxy
not ok 3 sync proxy
# (in test file fb-proxy.bats, line 26)
# `hammer capsule content synchronize --id=$PROXY_ID' failed with status 70
# Task 224e9fae-7fc4-494f-9188-c00c80a4874b running: 0.0/1, 0%, elapsed: 00:00:00
# Task 224e9fae-7fc4-494f-9188-c00c80a4874b warning: 1.0/1, 100%, 0.5/s, elapsed: 00:00:02
# Task 224e9fae-7fc4-494f-9188-c00c80a4874b warning: 1.0/1, 100%, 0.5/s, elapsed: 00:00:02
# Error: 404 Not Found
# 404 Not Found
# 404 Not Found
# 404 Not Found
ok 4 content is available from proxy
First seeing if 3.9 RC2 exhibits the same behavior, then will dig from there.