Invalid charm options while deploying mongodb

[Francesco Banconi]

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 https://jujucharms.com/trusty/mongodb#charm-config-opIdMem shows that the option is spelled differently("opIdMem" vs the "opidmem" in the error message).

[Richard Harding (rharding)]

Verified it also happens with 1.21.3

The v3 api has the correct case:
http://manage.jujucharms.com/api/3/charm/trusty/mongodb

As does the search api call:
https://api.jujucharms.com/charmstore/v4/search?text=mongodb&limit=1&include=charm-metadata&include=charm-config&include=bundle-metadata&include=extra-info&include=stats

The charm details configuration has the correct case in the title
https://10.0.3.238/trusty/mongodb-16/?text=mongodb#configuration

I clicked "add to canvas" and checked the case is correct in the database
app.db.services.item(1).config

And the commit/deploy worked.

Repeating the above with a drag/drop the db keys are lower case after the drop before the commit:
app.db.services.item(1).config

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)]

Fixed in https://github.com/juju/juju-gui/pull/701.