fix(e2e): Fix E2E test using kamelet my-own-timer-source

[gansheer]

ref #4750

Description

Remove duplicate usage of "my-own-timer-source" kamelet.

Release Note

fix(e2e): Fix E2E test using kamelet my-own-timer-source

[squakez]

LGTM. It's a best practice to use a different resource name. The problem is likely to be fixed, but the root cause probably will be there.

[gansheer]

LGTM. It's a best practice to use a different resource name. The problem is likely to be fixed, but the root cause probably will be there.

I agree, I could not find quickly the root cause. It could be some parallel test execution issue as the common tests run on a preinstalled operator.

[squakez]

It seems the change is breaking some other e2e test, is it that?

[gansheer]

It seems the change is breaking some other e2e test, is it that?

Unfortunately no, the one still in error was already failing before. I can't reproduce this failure on local env.

I will comment the code for now and add a comment in the current issue. As it is, it is not a documented behavior. I will keep it commented in case the failure become the signal we have another issues with kamelets.

[gansheer]

@squakez I think the refactoring fixed the issue. I am firing the CI to ensure the other failures were from an external source.

[squakez]

@squakez I think the refactoring fixed the issue. I am firing the CI to ensure the other failures were from an external source.

Okey. However, there's no need to force push just for re-running checks. Please ping any committer to just re-run the failing one in order to shorten the feedback cycle.