log bundle is practically empty

[Andrew Woodward]

found that support bundle on ISO 120 was effectively empty. It only contains psql dump

[Evgeniy L (rustyrobot)]

>> It only contains psql dump

Also it contains logs for 5 deployed nodes http://paste.openstack.org/show/76608/

But yeah, I don't see logs and configs for master node there.

[Evgeniy L (rustyrobot)]

I see a lot of errors during snapshot generation

Error occured: execve() argument 1 must be encoded string without NULL bytes, not str

[Openstack Gerrit (openstack-gerrit)]

Fix proposed to branch: master
Review: https://review.openstack.org/89541

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/89541
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=d6d416d8060cf3dfcc7bde4a95c44c443de9292c
Submitter: Jenkins
Branch: master

commit d6d416d8060cf3dfcc7bde4a95c44c443de9292c
Author: Evgeniy L <email address hidden>
Date: Tue Apr 22 13:52:51 2014 +0400

    Fixed diagnostic snapshot generation for master node

    * shlex in python 2.6 was broken and doesn't
      work correct with unicode, we have to
      encode it to ascii explicitly
    * fixed strings formating, use format
      method
    * fixed tests, use assertEqual instead of
      buildin assert method

    Closes-bug: #1310927
    Change-Id: I4a0746791d4317571d882416cfe75e8a41edf08a

[Andrey Sledzinskiy (asledzinskiy)]

verified on {"build_id": "2014-04-24_01-00-26", "mirantis": "yes", "build_number": "133", "nailgun_sha": "3e955a06aab9baf03210fef5d606971ef462be6c", "production": "prod", "ostf_sha": "134765fcb5a07dce0cd1bb399b2290c988c3c63b", "fuelmain_sha": "387d2e931ee14d5773f21f1e2860a13b50b37d04", "astute_sha": "6e8fa4cc12968d7b468fc590b2f06bb59bf74511", "release": "5.0", "fuellib_sha": "b9b8c1a951d777ece3b4dc400644ff1167f4fe01"}

[Bogdan Dobrelya (bogdando)]

In logs attached to https://bugs.launchpad.net/fuel/+bug/1373569 there are *still* empty commands.txt files in snapshot, looks like this bug wasn't fixed completely

[Bogdan Dobrelya (bogdando)]

The bug was reopened and re-targeted by mistake, I returned its status back, but I cannot assign it as Fix released in 5.0