manual: SupportedArchitecture restricts add-machine to same arch as bootstrap-host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Andrew Wilkins |
Bug Description
Some changes were made recently that restrict tools uploads to only those architectures that a provider/
Since add-machine ssh:... can be used to provision a machine of any architecture that *Juju* supports, the manual provider should simply allow any architecture.
Note that there's also a question of manually provisioning into non-manual environments. As long as we require that machines be on the same internal network (this is a current limitation of manual provisioning w/non-manual environments), then provisioning to architectures not supported by the environment is a moot point.
Related branches
- Juju Engineering: Pending requested
-
Diff: 52 lines (+5/-13)2 files modifiedprovider/manual/environ.go (+2/-7)
provider/manual/environ_test.go (+3/-6)
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | Ian Booth (wallyworld) → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Marking critical, because 1.17.7 may turn into 1.18, which is when manual is supposed to be "ready".