'returncode: null' is reported in a post-installation test for saucy server smoke test

[Para Siva]

In Saucy server floodlight post installation test, test_openflow, the outcome of the test is not clear since 'returncode: null' is reported in the output yaml file. The stderr is also left empty. The installation appear to go well though. Occurs on both amd64 and i386.

The impacted jobs are,
https://jenkins.qa.ubuntu.com/view/Saucy/view/Smoke%20Testing/job/saucy-server-amd64-smoke-floodlight/11/
and
https://jenkins.qa.ubuntu.com/view/Saucy/view/Smoke%20Testing/job/saucy-server-i386-smoke-floodlight/9/

The test that's impacted is,
http://bazaar.launchpad.net/~ubuntu-server-dev/ubuntu-test-cases/server-tests-raring/view/head:/testsuites/floodlight/test_openflow/test.py

[Andy Doan (doanac)]

This seems to work on raring. When running on saucy the first time i got a weird encode/decode error. When re-running it passed. Going to re-provision and see if I can repeat.

[Andy Doan (doanac)]

I think this may have been caused by bad timing. I can't reproduce it anymore and I think its because of the unicode fix we added in utah-client 0.12.2