Deployments on non-amd64 architectures is not transparent anymore
Bug #1966195 reported by
Konstantinos Tsakalozos
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Unassigned | ||
Bug Description
Deploying the ubuntu charm on ARM64 is failing if i do not specify the architecture:
```
07:42:37 2022-03-24 at 05:42:37 | INFO + juju deploy -m release-
07:42:45 2022-03-24 at 05:42:45 | INFO ERROR cannot add application "ubuntu": invalid AWS instance type "a1.2xlarge" and arch "amd64" specified
```
This used to work fine. Now I have to be explicit and set the architecture as a constraint (`--constraints 'instance-
| description: | updated |
Revision history for this message
| Harry Pidcock (hpidcock) wrote | #1 |
| Changed in juju: | |
| importance: | Undecided → High |
| milestone: | none → 2.9-next |
| status: | New → Triaged |
| Changed in juju: | |
| milestone: | 2.9-next → none |
To post a comment you must log in.
Juju should try its best to introspect the cloud as to what the architecture is for a set of constraints.