Invalid charm options while deploying mongodb

Bug #1428751 reported by Francesco Banconi on 2015-03-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kyle Adams

Bug Description

The GUI fails to deploy the mongodb charm due to unrecognized options.
To dupe:
- deploy the GUI in a real env: I used juju devel (1.22-beta4-utopic-amd64);
- search for mongodb;
- drag and drop the charm;
- click commit.

The service deployment fails ("Could not deploy the requested service. Server responded with: unknown option opidmem" or similar). The JS console show an "Uncaught TypeError: Cannot read property 'get' of null".
The service in the canvas is left in uncommited state and the GUI is no longer usable.

It might be a red herring but shows that the option is spelled differently("opIdMem" vs the "opidmem" in the error message).

Richard Harding (rharding) wrote :

Verified it also happens with 1.21.3

The v3 api has the correct case:

As does the search api call:

The charm details configuration has the correct case in the title

I clicked "add to canvas" and checked the case is correct in the database

And the commit/deploy worked.

Repeating the above with a drag/drop the db keys are lower case after the drop before the commit:

So this is a case where the drag/drop path goes through something that is lower casing the keys of the service config causing the error on the Juju end once we attempt to commit.

Kyle Adams (kadams54) on 2015-03-05
Changed in juju-gui:
assignee: nobody → Kyle Adams (kadams54)
Kyle Adams (kadams54) wrote :
Changed in juju-gui:
status: Triaged → Fix Committed
Changed in juju-gui:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers