profile list returns non-zero if a cluster is not running

[medyagh]

when I was looking at this intergeration test that failed because profile list says one of the clusters is not running yet...

https://storage.googleapis.com/minikube-builds/logs/6717/e653589/Docker_Linux.html#fail_TestFunctional%2fparallel%2fProfileCmd%2fprofile_list

and also one of the users who was using minikube in a test script,... made me think.

When are the resonable times to exit none-zero for profile list ?

currently we exit non-zero for the following:

• If there is no profile .
• if there are a few profiles are one of them has error to give status running.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[tstromberg]

I think we should emulate the output of:

kubectl po -A
docker ps

These two commands do not error if one of the pods/containers is not running.

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[MadhavJivrajani]

/remove-kind design
/kind feature
kind/design is migrated to kind/feature, see kubernetes/community#6144 for more details