After upgrading to Pipelines 1.7.1, tasks are failing when "init" is the first argument followed by two or more other arguments.

Customer reports that in OCP pipelines 1.7.1, running a task with init as the first argument followed by any two arguments causes the task to fail.

We have tried to test this and could see the exact same result.

The thing to note here is that any change in the issue above, say changing init to some other word or adding or removing arguments does not affect the task run.

The issue has been experimented with a UBI minimal image and I see the same results.
We tried to just run the image as a container and pass arguments which work fine.

We also tried to compare the yaml files of failed pods of tekton tasks with the completed ones, but see no major difference.