Description of problem:

When setting up a Pipeline manually the Pipeline Run failed (with the steps described below) which results in an unexpected Pipeline Run Status. When checking the logs for the Pipeline Run a "random" Pod log was shown to the user.
Prerequisites (if any, like setup, operators/versions):

    Install OpenShift Pipelines operator (tested with 1.0.1)

Steps to Reproduce

    Create a project / namespace
    Create at least one (or better more) other running pods (ex. from image jerolimov/nodeinfo)
    Create a pipeline (Pipeline > Create)
    1. Select Task "git-clone"
    2. Select Task "git-clone" and enter a Git url (ex. https://github.com/jerolimov/docker)
    3. Press create
    Run the new Pipeline and checkout the logs
    1. Select Action dropdown > Start
    2. Select the Logs tab
    You now see log messages from other pods!

Actual results:

    You now see log messages from other pods!

There was the following error messages part of the Pipeline run:

    Pipeline run message: TaskRun new-pipeline-6a827s-git-clone-bv7jp has failed
    TaskRun message: bound workspaces did not match declared workspaces: didn't provide required values: [output]

Expected results:

    Do not show an invalid pod log. Do not request Pods without a name filter.
    Show the correct log message, or at least an error message:
    Show the PipelineRun status condition message, or better the taskRun status condition message!

Reproducibility (Always/Intermittent/Only Once):

Always
Build Details:
Additional info:

Select your Pipeline Ruin Details and open the YAML.

Under "taskRuns xxx status" you can see that the "podName" is an empty (""). First analyse with Andrew Ballantyne shows that this is used to select "the first pod within your namespace" because the name filter was not applied.

See also packages/dev-console/src/components/pipelineruns/detail-page-tabs/PipelineRunLogs.tsx