Loading local avalanched binary to S3 fails
exdx opened this issue · 2 comments
exdx commented
When using a local version of avalanched, uploading to S3 no longer works as expected:
STEP: upload artifacts to S3 bucket
[2023-07-20T14:24:05Z INFO aws_manager::s3] put object '/Users/dan.sover/avalanched-aws' (size 40.42 MB) to 's3://avalanche-ops-202307-4lw5xroxbc-us-west-2/aops-custom-202307-HQhBUm/bootstrap/install/avalanched-aws' (region 'us-west-2')
[2023-07-20T14:24:05Z INFO aws_manager::s3] put_byte_stream_with_metadata to 's3://avalanche-ops-202307-4lw5xroxbc-us-west-2/aops-custom-202307-HQhBUm/bootstrap/install/avalanched-aws' (region 'us-west-2')
thread 'main' panicked at 'failed put_object upload_artifacts.avalanched_bin: API { message: "failed put_object request has timed out", retryable: true }', avalancheup-aws/src/apply/mod.rs:257:18
I have confirmed that I am logged in to s3 and can see the bucket being used when running aws s3 ls --profile <PROFILE>
.
This regression may be a result of switching identity providers.
exdx commented
Also monitoring a similar failure in install-subnet-chain
let subnet_config_s3_key = format!(
"{}{}",
s3::append_slash(&opts.s3_key_prefix),
file_stem.to_str().unwrap()
);
s3_manager
.put_object(
&opts.subnet_config_local_path,
&opts.s3_bucket,
&subnet_config_s3_key,
)
.await
.expect("failed put_object subnet_config_path");
fails locally, unexpectedly
exdx commented
We added retries so I will close this issue for now. We can reopen if necessary.