Revert of Set BOTO_CONFIG correctly in cloud_storage.py

Revert of Set BOTO_CONFIG correctly in cloud_storage.py (patchset #1 id:1 of https://codereview.chromium.org/2923123006/ )

Reason for revert:
It turns out this did not fix the issue on the buildbot. The .boto file might be on the buildbot at this path, but the tests that are failing are running inside a VM, and don't have access to it in the first place.

Another approach is needed to fix the linked bug, and we will likely put a .boto file in the home directory that is being set when running gsutil.

Original issue's description:
> Set BOTO_CONFIG correctly in cloud_storage.py
> 
> When running the telemetry perf tests on a VM host as root, the .boto was not
> being found.
> 
> This patch simply sets the BOTO_CONFIG environment variable to point at
> the correct location.
> 
> Bug: chromium:712349
> Review-Url: https://codereview.chromium.org/2923123006
> Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/23ac69b72e05e6d1788c915353bdd75dd596f1e7

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.

Review-Url: https://codereview.chromium.org/2931173002
Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/f3c416239e8ac0ce2962714f1b6e70da709198a6

[lpique, 2017-06-09 19:32:40]

The CQ bit was checked by lpique@chromium.org

[lpique, 2017-06-09 19:32:40]

Created Revert of Set BOTO_CONFIG correctly in cloud_storage.py

[commit-bot: I haz the power, 2017-06-09 19:32:50]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-06-09 19:32:50]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-06-09 19:32:51]

No L-G-T-M from a valid reviewer yet.
CQ run can only be started once the patch has received an L-G-T-M from a full
committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,_not_ a
full super star committer.
Committers are members of the group "project-catapult-committers".
Note that this has nothing to do with OWNERS files.

[lpique, 2017-06-09 19:35:58]

Looks like I need an LGTM first. PTAL.

[nednguyen, 2017-06-09 19:36:43]

lgtm

[lpique, 2017-06-09 19:37:14]

The CQ bit was checked by lpique@chromium.org

[commit-bot: I haz the power, 2017-06-09 19:37:20]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-06-09 20:02:13]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1497037034065970, "parent_rev":
"4ef4b9509fe15a757ad506be6bac48070eb945d3", "commit_rev":
"f3c416239e8ac0ce2962714f1b6e70da709198a6"}

[commit-bot: I haz the power, 2017-06-09 20:02:17]

Description was changed from

==========
Revert of Set BOTO_CONFIG correctly in cloud_storage.py (patchset #1 id:1 of
https://codereview.chromium.org/2923123006/ )

Reason for revert:
It turns out this did not fix the issue on the buildbot. The .boto file might be
on the buildbot at this path, but the tests that are failing are running inside
a VM, and don't have access to it in the first place.

Another approach is needed to fix the linked bug, and we will likely put a .boto
file in the home directory that is being set when running gsutil.

Original issue's description:
> Set BOTO_CONFIG correctly in cloud_storage.py
> 
> When running the telemetry perf tests on a VM host as root, the .boto was not
> being found.
> 
> This patch simply sets the BOTO_CONFIG environment variable to point at
> the correct location.
> 
> Bug: chromium:712349
> Review-Url: https://codereview.chromium.org/2923123006
> Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
==========

to

==========
Revert of Set BOTO_CONFIG correctly in cloud_storage.py (patchset #1 id:1 of
https://codereview.chromium.org/2923123006/ )

Reason for revert:
It turns out this did not fix the issue on the buildbot. The .boto file might be
on the buildbot at this path, but the tests that are failing are running inside
a VM, and don't have access to it in the first place.

Another approach is needed to fix the linked bug, and we will likely put a .boto
file in the home directory that is being set when running gsutil.

Original issue's description:
> Set BOTO_CONFIG correctly in cloud_storage.py
> 
> When running the telemetry perf tests on a VM host as root, the .boto was not
> being found.
> 
> This patch simply sets the BOTO_CONFIG environment variable to point at
> the correct location.
> 
> Bug: chromium:712349
> Review-Url: https://codereview.chromium.org/2923123006
> Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...

TBR=nednguyen@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.

Review-Url: https://codereview.chromium.org/2931173002
Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2017-06-09 20:02:18]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...