ensemble state saved in S3 is broken
Bug #613987 reported by
Gustavo Niemeyer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
High
|
Kapil Thangavelu |
Bug Description
We must fix the following problems in the state saved in S3:
1) It's being saved as a Python tuple in YAML. Should be a list.
2) It has an empty string as the second element of the tuple, somehow
3) We should really name it as "provider-state" or something similar, rather than "ensemble" (everything is ensemble)
Related branches
lp:~hazmat/pyjuju/lp-613987-ensemble-s3-state-normalization
- Gustavo Niemeyer: Approve
-
Diff: 232 lines (+26/-28)6 files modifiedensemble/providers/ec2/connect.py (+1/-1)
ensemble/providers/ec2/launch.py (+3/-4)
ensemble/providers/ec2/state.py (+2/-2)
ensemble/providers/ec2/tests/test_connect.py (+5/-6)
ensemble/providers/ec2/tests/test_launch.py (+10/-10)
ensemble/providers/ec2/tests/test_state.py (+5/-5)
description: | updated |
Changed in ensemble: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in ensemble: | |
assignee: | nobody → Kapil Thangavelu (hazmat) |
Changed in ensemble: | |
status: | Confirmed → In Progress |
Changed in ensemble: | |
status: | In Progress → Fix Committed |
Changed in ensemble: | |
milestone: | none → 0.1 |
Changed in ensemble: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The empty string is potentially expected, as the newly launched machine may not have a dns name. Its probably worthwhile to just drop it entirely, esp. if we move the tunnel to a daemon, as the resolution/ connection would be a one time cost, and we have to validate the state regardless.