Floating IP ids are string in grizzly

Bug #1174513 reported by Patrick Hetu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Go OpenStack Exchange
Fix Released
Undecided
Unassigned

Bug Description

Juju-core fail to bootstrap with a json decoding error because in the FloatingIP struct Id is a int and not a string.

I've change it to a string and it bootstrapped. I don't know the implication of this for folom thought.

Revision history for this message
Patrick Hetu (patrick-hetu) wrote :
Revision history for this message
Данило Шеган (danilo) wrote :

Patrick, thanks for the bug report and a patch. This has since been fixed in juju-core.

Revision history for this message
Данило Шеган (danilo) wrote :

Whoops, I've misread the current code. It hasn't been fixed.

Can you please elaborate on what are you doing to get this bug? Environment details, command line parameters and any non-default configs that you are using would help.

We haven't seen problems like these ourselves.

Changed in goose:
status: New → Incomplete
Revision history for this message
Patrick Hetu (patrick-hetu) wrote :

I realized that my bug looks a lot like: https://bugs.launchpad.net/goose/+bug/1188815
but for floating IP. I'm also using quantum/Grizzly and have the same error message:

json: cannot unmarshal string into Go value of type int

Changed in goose:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.