Instance type constraint throws "ambiguous constraints" error on GCP
Bug #1970462 reported by
Stone Preston
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Harry Pidcock | ||
Bug Description
This bug is similar to https:/
im trying to deploy a GPU-enabled ck worker on GCP using the following command:
juju deploy kubernetes-worker --channel=1.24/edge --constraints "instance-
but it yields the following error:
ERROR cannot add application "kubernetes-
even though I am only specifying the instance type, which the docs (https:/
| Changed in juju: | |
| assignee: | nobody → Jordan Barrett (barrettj12) |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| assignee: | Jordan Barrett (barrettj12) → nobody |
| importance: | Medium → High |
| milestone: | none → 2.9.30 |
| Changed in juju: | |
| milestone: | 2.9.30 → 2.9-next |
| milestone: | 2.9-next → 2.9.31 |
| Changed in juju: | |
| assignee: | nobody → Harry Pidcock (hpidcock) |
Revision history for this message
| Harry Pidcock (hpidcock) wrote | #2 |
Revision history for this message
| Harry Pidcock (hpidcock) wrote | #3 |
| Changed in juju: | |
| status: | Triaged → Fix Committed |
| Changed in juju: | |
| milestone: | 2.9.31 → 2.9.30 |
| milestone: | 2.9.30 → 2.9.31 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is fall out from the need to explicitly specify arch when dealing with charmhub (we previously could leave arch empty since charm store only served one blob for any arch).
We'll need to figure out the best path forward, and it needs to be High priority.