Open sdimitro opened 1 year ago
Problem seems to stem from here: https://github.com/delphix/appliance-build/blob/a5936cd05378a303b06da8dc59705567382e7205/scripts/upgrade-image-from-aptly-repo.sh#L160
if [[ -n "${DELPHIX_SIGNATURE_TOKEN:-}" ]] && [[ -n "${DELPHIX_SIGNATURE_URL:-}" ]]; then
echo "{\"data\": \"$(base64 -w 0 SHA256SUMS)\"}" >sign-request.payload ||
die "failed to generate sigh-request.payload file"
#
# Here, we need to generate signature files for all of the appliance
# versions that'll be allowed to upgrade from, using this upgrade
# image. We rely on the user of this script to pass in this list
# of versions; generally this will be some Jenkins automation.
#
for signature_version in $DELPHIX_SIGNATURE_VERSIONS; do
curl -s -S -f -H "Content-Type: application/json" \
-u "$DELPHIX_SIGNATURE_TOKEN" -d @sign-request.payload \
"$DELPHIX_SIGNATURE_URL/upgrade/keyVersion/${signature_version}/sign" \
>sign-request.response ||
die "failed to generate sign-request.response file"
We got a 404 from the $DELPHIX_SIGNATURE_URL/...etc.../${signature_version}/sign. Unfortunately the logs don't tell us where this came from so I'll probably need to rerun the job in a bootstrap VM.
That means that the signing server threw a 404 when you tried to get the signature... Possibly the signing server removed support for an old key version that the appliance-build repo still tries to use?
link: http://ops.jenkins.delphix.com/job/appliance-build-stage0/job/post-push/4745/execution/node/295/log/