juju-deployer deploys the wrong unit series from charm store
Bug #1643027 reported by
Ryan Beisner
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Charm Test Infra |
Confirmed
|
Medium
|
Ryan Beisner | ||
OpenStack Charm Testing |
Confirmed
|
High
|
Ryan Beisner | ||
juju-deployer |
Invalid
|
Low
|
Unassigned |
Bug Description
juju-deployer (with juju 1.25) deploys the wrong series unit from the charm store.
⟫ pip freeze
backports.
juju-deployer=
jujuclient==0.53.3
pkg-resources=
PyYAML==3.12
six==1.10.0
websocket-
Changed in charm-test-infra: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in openstack-charm-testing: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in charm-test-infra: | |
assignee: | nobody → Ryan Beisner (1chb1n) |
Changed in openstack-charm-testing: | |
assignee: | nobody → Ryan Beisner (1chb1n) |
To post a comment you must log in.
Further clarification:
juju-deployer remains a critical library in the charm test story, as Amulet uses juju-deployer, whether Juju 1.x or Juju 2.x, and Bundletester uses Amulet.
The OSCI test gate is blocked for testing any series other than Xenial at this time.