Wrong prow status during Jenkins parallel pipeline test

[smoshiur1237]

We are having an issue where prow Jenkins operator is not supporting Jenkins parallel pipelines. Since migrating from ghprb, we have noticed instances where tests triggered from prow reported as passed on GitHub, while some of the parallel stages had failed/aborted on Jenkins.

The issue reproduced in the following test PR where it has parallel Jenkins job was running: Test PR . Here we can see metal3-centos-e2e-feature-test-main — Jenkins job succeeded. status for parallel run even though only one test was passing and two other tests were aborted/failed. Jenkins Reproduction 1 , Jenkins Reproduction 2

Also, adding the link to the parallel test pipeline code which was working properly before the prow migration from ghprb.

We expect to have correct prow response in case of any failure in the parallel test pipeline. In the above test cases prow response status should haveFailurestatus instead of Success.

[smoshiur1237]

Increasing max prowjob age PR to 24h is not solving this issue. I can reproduce the issue in the following jenkins run on the Test PR.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue 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.

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[tuminoid]

/remove-lifecycle rotten
This is still an issue.

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[tuminoid]

/remove-lifecycle stale

This is still valid issue.