Config rendering broken on the Hadoop charm
Bug #1201950 reported by
Jorge Castro
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charmworld |
Fix Released
|
High
|
Curtis Hovey | ||
Bug Description
http://
In both Firefox and Chrome.
" dfs%2Eblock%2Esize int " and so on.
Related branches
lp:~sinzui/charmworld/stale-metadata
- Brad Crittenden (community): Approve (code)
-
Diff: 112 lines (+34/-17)3 files modifiedcharmworld/jobs/ingest.py (+7/-6)
charmworld/jobs/tests/test_scan.py (+26/-9)
charmworld/testing/factory.py (+1/-2)
| affects: | juju-gui → charmworld |
| Changed in charmworld: | |
| importance: | Undecided → High |
| status: | New → Triaged |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #2 |
| Changed in charmworld: | |
| assignee: | nobody → Curtis Hovey (sinzui) |
| status: | Triaged → Fix Committed |
| Changed in charmworld: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This might be caused by a recent mongodb schema change where user data such as config and metadata were moved to be values because we didn't want arbitrary user data as db keys. This might also have been corrected by ingest, but bug 1201612 shows that new historic charms are bot getting metadata and config data changes. If this bug is not fixed by the other bug, then we want to look at the cases where ingest quotes the metadata and config keys. I think the current schema cannot ever use them as keys, so the quoting can be removed.