Adjust instructions for refreshing skolo service account When the metadata server is rebuilt a CL is generated to update the version pin in the k8s-config repo. Running the jumphosts playbook immediately after build_and_release_metadata_server_ansible results in the old version being pushed if the CL hasn't landed yet. Bug: b/382236823 Change-Id: Ie87749ef3142b42bcd2be3ef6605f81f41c090fd Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/926977 Auto-Submit: Eric Boren <borenet@google.com> Reviewed-by: Kaylee Lubick <kjlubick@google.com> Commit-Queue: Kaylee Lubick <kjlubick@google.com>
diff --git a/skolo/refresh-skolo-swarming-bot-service-account-keys.sh b/skolo/refresh-skolo-swarming-bot-service-account-keys.sh index 68809b0..eeb1e04 100755 --- a/skolo/refresh-skolo-swarming-bot-service-account-keys.sh +++ b/skolo/refresh-skolo-swarming-bot-service-account-keys.sh
@@ -8,4 +8,5 @@ printf 'You should now run:\n' printf ' cd ansible\n' printf ' ansible-playbook ./switchboard/build_and_release_metadata_server_ansible.yml\n' +printf ' (wait for the CL to update the metadata server to land)\n' printf ' ansible-playbook ./switchboard/jumphosts.yml\n' \ No newline at end of file