Pipeline get stuck into orange (error) state but did not show any logs or error details just loading.

[nileshav]

Summary

We are facing one issue, that pipeline is get stuck in orange state and just showing loading status without any error details at frontend. We are quite confused to investigate because the no error shown and stuck the pipeline in orange state.

Steps to reproduce

When we pin particular resource then pipeline successfully work with error (No such file or directory) for that particular resource but when we unpin that resource then pipeline stuck in orange state. (snapshot attached)

Expected results

Orange state of pipeline must show any error log or statement.

Actual results

Orange state of pipeline showing only the loading into frontend UI of concourse.

Additional context

We are trying to run a build by without pin version for a resource which should work.
We have found slight similar issue reported #6399

Triaging info

• Concourse version: 7.8.2
• Browser (if applicable): Edge/Chrom
• Did this used to work? not sure

[pmatuska]

Additional information:

It looks like this is happening when we have two resources of git resource type (for 2 different branches of the same repo, main and feature branch), where the feature branch was created from the main branch but does not contain any new commits yet (so both have the same commit ID as latest).

Example:

Main branch resource:

Target branch resource:

[jenszo]

I can also confirm this is affecting multiple project teams. Looking forward to a few insights.

[tatyango]

interested in this request as well.

[nileshav]

Hello Concourse Team,

Checking for an update.

[nileshav]

Hello Concourse Team,

Checking for an update.

[suhlig]

We're having the same problem and the only workaround is to remove one of the resources. Re-adding it makes the problem re-appear.

[taylorsilva]

More information is needed. How did the pipeline get in this state where pinning/unpinning leads to builds being "oranged" or not "oranged". More logs from the web node might help, specifically filtering down for logs related to this pipeline.