hack/{verify,update}-bazel.sh are broken

[cjwagner]

hack/update-bazel.sh is no longer working. This looks like the most recent change: #24006
Here is an example error using bazel from the image:

./hack/update-bazel.sh
FATAL: $USER is not set, and unable to look up name of current user: (error: 0): Success

And here is a different error using bazel directly:

./hack/verify-bazel.sh 
go: downloading github.com/bazelbuild/buildtools v0.0.0-20211007154642-8dd79e56e98e
+ bazel test --test_output=streamed @io_k8s_repo_infra//hack:verify-bazel
INFO: Repository py_deps instantiated at:
  no stack (--record_rule_instantiation_callstack not enabled)
Repository rule pip_import defined at:
  /home/colew/.cache/bazel/_bazel_colew/eae8e63a8a5cb158e706f8e5ee2736a4/external/rules_python/python/pip.bzl:44:29: in <toplevel>
ERROR: An error occurred during the fetch of repository 'py_deps':
   pip_import failed:  (src/main/tools/process-wrapper-legacy.cc:75: "execvp(python2.7, ...)": No such file or directory
)
INFO: Reading rc options for 'test' from /home/colew/.gvm/pkgsets/go1.16.2/global/src/k8s.io/test-infra/.bazelrc:
  'test' options: --@io_bazel_rules_go//go/config:race --test_output=errors --build_tests_only
ERROR: @io_bazel_rules_go//go/config:race :: Error loading option @io_bazel_rules_go//go/config:race: no such package '@py_deps//': pip_import failed:  (src/main/tools/process-wrapper-legacy.cc:75: "execvp(python2.7, ...)": No such file or directory
)

PR with error: #24042
It is also concerning that this indicates success when using bazel from the image even though it actually failed.

/assign @cjwagner @chaodaiG

[cjwagner]

/sig testing

Looks like all bazel commands may be affected by this...
I don't think we've changed the python bazel targets yet (ref: #24034) so I'm not sure what change could have caused python2.7 to start being required locally.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.