[flake] Sometimes GH workflows do not run on PRs

[tuminoid]

Which jobs are failing?

Github workflows (e2e). They are not created for newly created PRs, or they might go missing when PR is rebased or content amended.

Which tests are failing?

They're not run at all. Not visible in the test table, unless PR is renamed or edited somehow that retriggers the workflows.

Since when has it been failing?

Maybe past 6 months.

Jenkins link

No response

Reason for failure (if possible)

No response

Anything else we need to know?

No response

Label(s) to be applied

/kind failing-test
/area ci

[metal3-io-bot]

@tuminoid: The label(s) area/ci cannot be applied, because the repository doesn't have them.

In response to this:

Which jobs are failing?

Github workflows (e2e)

Which tests are failing?

They're not run at all. Not visible in the test table, unless PR is renamed or edited somehow that retriggers the workflows.

Since when has it been failing?

Maybe past 6 months.

Jenkins link

No response

Reason for failure (if possible)

No response

Anything else we need to know?

No response

Label(s) to be applied

/kind failing-test
/area ci

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-sigs/prow repository.

[tuminoid]

/triage accept

[metal3-io-bot]

@tuminoid: The label(s) triage/accept cannot be applied, because the repository doesn't have them.

In response to this:

/triage accept

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-sigs/prow repository.

[tuminoid]

/triage accepted

[tuminoid]

We have so many of these today with dependabot's controller-runtime PRs... Even after rebases, same PRs always lack the actions, despite retitleing to get them to run.