DescriptionUpdated how unitName is sent to resolve/retry
The inspector was create an array[array] and thus passing the resovled()
method an array as a unitName. The go back end expects a string and it
refused to resolve/retry anything.
- Update the inspector method to make sure it grabs a single string
- Update the tests for the inspector to look for a single string
- Add a quick assertion in the go backend to fuss if it doesn't get a string
QA:
Note: MySQL always fails for me in my local lxc go environment
- Bootstrap a go environment in lxc, deploy mysql into it. I setup 3 units.
- Wait for the units to go into error state.
- Pick one of the units, resolve the unit.
- After a bit it should go to running and you can destroy it properly.
- Note that you can also watch the WS traffic in chrome dev tools and verify
that your request/response was successful.
Example broken communication:
{"RequestId":31,"Error":"json: cannot unmarshal array into Go value of type string","Response":{}}
{"Type":"Client","Request":"Resolved","Params":{"UnitName":["mysql/0"],"Retry":false},"RequestId":32}
https://code.launchpad.net/~rharding/juju-gui/go-resolve-retry/+merge/185565
(do not edit description out of merge proposal)
Patch Set 1 #
Total comments: 2
Patch Set 2 : Updated how unitName is sent to resolve/retry #
MessagesTotal messages: 5
|