aws juju bootstrap fails; cannot connect to juju-released-tools url

Bug #1924775 reported by Alexander Balderson on 2021-04-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Critical
John A Meinel

Bug Description

When trying to juju boostrap on aws I get an invalid url while trying to get product data.

It seems the URL https://juju-dist.s3.amazonaws.com/tools/streams/v1/com.ubuntu.juju-released-tools.sjson is giving a permission denied.

logs from the test run are below.

2021-04-16-11:46:50 root DEBUG [localhost]: juju bootstrap --config bootstrap-timeout=1800 --model-default /home/ubuntu/project/generated/model_defaults.yaml aws foundations-aws
2021-04-16-11:46:52 root DEBUG Creating Juju controller "foundations-aws" on aws/us-east-1
2021-04-16-11:46:57 root DEBUG Looking for packaged Juju agent version 2.8.10 for amd64
2021-04-16-11:46:58 root DEBUG ERROR failed to bootstrap model: cannot read product data, invalid URL "https://juju-dist.s3.amazonaws.com/tools/streams/v1/com.ubuntu.juju-released-tools.sjson" not found
2021-04-16-11:47:03 root ERROR [localhost] Command failed: juju bootstrap --config bootstrap-timeout=1800 --model-default /home/ubuntu/project/generated/model_defaults.yaml aws foundations-aws
2021-04-16-11:47:03 root ERROR [localhost] STDOUT follows:

2021-04-16-11:47:03 root ERROR [localhost] STDERR follows:
Creating Juju controller "foundations-aws" on aws/us-east-1
Looking for packaged Juju agent version 2.8.10 for amd64
ERROR failed to bootstrap model: cannot read product data, invalid URL "https://juju-dist.s3.amazonaws.com/tools/streams/v1/com.ubuntu.juju-released-tools.sjson" not found

Pete Vander Giessen (petevg) wrote :

Investigating, it looks like the buckets are still there:

https://paste.ubuntu.com/p/XwPJB2nkZb/

The access permissions aren't set correctly. I pinged IS to see if this is due to a change on their part.

Changed in juju:
status: New → In Progress
assignee: nobody → Pete Vander Giessen (petevg)
milestone: none → 2.9-rc11
assignee: Pete Vander Giessen (petevg) → nobody
assignee: nobody → John A Meinel (jameinel)
importance: Undecided → Critical
John A Meinel (jameinel) wrote :

This should now be fixed. It was related to an account change that we have reverted, but we will look to move that account to be managed by IS so that we have more visibility on it (especially across multiple timezones).

Changed in juju:
milestone: 2.9-rc11 → none
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers