A mongodb-relation-changed hook called out to a python3 script to import some data into mongodb.
The python script encountered a unicode error:
2014-06-19 20:23:17 INFO mongodb-relation-changed Traceback (most recent call last):
2014-06-19 20:23:17 INFO mongodb-relation-changed File "/opt/openmotion/import.py", line 194, in
2014-06-19 20:23:17 INFO mongodb-relation-changed parse_bikes(mongo_uri)
2014-06-19 20:23:17 INFO mongodb-relation-changed File "/opt/openmotion/import.py", line 155, in parse_bikes
2014-06-19 20:23:17 INFO mongodb-relation-changed stations = parser1
2014-06-19 20:23:17 INFO mongodb-relation-changed File "/opt/openmotion/import.py", line 81, in parse_valencia_bikes
2014-06-19 20:23:17 INFO mongodb-relation-changed json_data = open(basepath + 'data/bikes/Valenbisi.JSON').read()
2014-06-19 20:23:17 INFO mongodb-relation-changed File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode
2014-06-19 20:23:17 INFO mongodb-relation-changed return codecs.ascii_decode(input, self.errors)[0]
2014-06-19 20:23:17 INFO mongodb-relation-changed UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 272: ordinal not in range(128)
2014-06-19 20:23:17 ERROR juju.worker.uniter uniter.go:482 hook failed: exit status 1
Running the same script from a terminal on the same node succeeded.
After further debugging, I determined that the mongodb-relation-changed hook does not set any locale.
Adding:
export LANG=en_US.UTF-8
to the hook allowed the import script to succeed.
Note: although this enabled me to make progress on writing my hook, I think upstream needs to take a closer look. I am not an expert on locales, and I wonder if forcing en_US.UTF-8 on all juju users is appropriate or not...
Copied from github (also see discussion there): https://github.com/juju/juju/issues/133
The traceback is showing a bug in the mongodb charm:
2014-06-19 20:23:17 INFO mongodb-
It is attempting to open a file in text mode without specifying the encoding, which will fail in some environments. You could force the system locale, which would mean this bug would only be triggered in locales not using UTF-8 encoding. Forcing a specific locale is not really appropriate, as if you are not using the system locale or you will end up with much harder to solve problems (things being sorted in the wrong order, unreadable filenames).
As the preferred encoding of JSON is UTF-8, the fix is to specify this in the open call (if you want read() to return unicode text), or open the file in binary mode if you want a UTF-8 encoded byte string.