-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PipelineRun validation error for params without a type #4258
Comments
Here's the simplest example that fails for me...
What I've found is that in any version "after" 0.26.0 when I apply I will get...
If I do a
I've now verified that I get the same result with 0.27.0, 0.27.2, 0.27.3, and 0.28.0 I use different flavors of Kubernetes but all version 1.20 and am only seeing this with openshift 4.7.x (currently using 4.7.30 but saw this with 4.7.21 too). I'm truly at a loss as to what's changed between 0.26.0 and 0.27.0 that could cause this. |
I can reproduce the issue.
If I create a |
With this change in:
I now get a different error:
|
After updating from 0.26.0 to 0.27.3 we're seeing the following error...
The pipeline in question here declares a "cluster", "repository", and "revision" param but does not specify a "type" for these params as the default type has worked until now. We've found that if we alter the Pipeline definition to specify
type: string
for these params everything works correctly.Reporting now in the hope someone can think of some difference between 0.26 and 0.27.x , but we're trying to create a good reproducer...
The problem occured in a moderately complex pipeline. We've tried a super simple hello world pipeline where we did not declare a type on a param but it worked. That leads us to believe that perhaps there is a race condition between when the default type is set and someone checks it?? We have so far only seen this in our Openshift 4.7 (RHEL7) cluster and not our vanilla Kubernetes cluster but that might not be ultimately relevant.
The text was updated successfully, but these errors were encountered: