updated yaml package requires a Loader
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AWS Integrator Charm |
Fix Released
|
High
|
Adam Dyess | ||
Google Cloud Platform Integrator Charm |
Fix Released
|
High
|
Adam Dyess | ||
vSphere Integrator Charm |
Fix Released
|
High
|
Adam Dyess |
Bug Description
Each of the edge charms are affected by an issue with what seems to be a new version of yaml that affects the charm.
1.28/edge, 1.29/edge, latest/edge charms
unit-gcp-
Traceback (most recent call last):
File "/var/lib/
bus.
File "/var/lib/
_invoke(
File "/var/lib/
handler.
File "/var/lib/
self.
File "/var/lib/
toggle_
File "/var/lib/
creds = yaml.load(
TypeError: load() missing 1 required positional argument: 'Loader'
Swapping out to yaml.safe_load() should fix it
Changed in charm-gcp-integrator: | |
milestone: | none → 1.28+ck1 |
assignee: | nobody → Adam Dyess (addyess) |
status: | New → Triaged |
importance: | Undecided → High |
Changed in charm-aws-integrator: | |
milestone: | none → 1.28+ck1 |
assignee: | nobody → Adam Dyess (addyess) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in charm-vsphere-integrator: | |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Adam Dyess (addyess) |
milestone: | none → 1.28+ck1 |
Changed in charm-aws-integrator: | |
status: | Triaged → Fix Committed |
Changed in charm-gcp-integrator: | |
status: | Triaged → Fix Committed |
Changed in charm-vsphere-integrator: | |
status: | Triaged → Fix Committed |
tags: | added: backport-needed |
Changed in charm-aws-integrator: | |
status: | Fix Committed → Fix Released |
Changed in charm-gcp-integrator: | |
status: | Fix Committed → Fix Released |
Changed in charm-vsphere-integrator: | |
status: | Fix Committed → Fix Released |
https:/ /github. com/juju- solutions/ charm-vsphere- integrator/ pull/13 /github. com/juju- solutions/ charm-gcp- integrator/ pull/17 /github. com/juju- solutions/ charm-aws- integrator/ pull/49
https:/
https:/
Addressing in 3/4 of the cloud integrator charms
charm-openstack -integrator never seems to have had this issue