Created attachment 1652426 [details]
Created attachment 1652427 [details]
Latest 4.2 CI build
I tried to validate this bug on latest stable 4.2 which is 4.2.14 and on latest 4.2 CI build which is 4.2.0-0.ci-2020-01-15-023211 but I am unable to validate it. Should I wait till 21st Jan when the next stable 4.2 will be released which will be 4.2.15 to validate this bug?
Please find the attached screenshots.
That's most bizarre... it should have been merged into the CI. I found it in the nightly listed builds but the backlog of CI builds is half as big so I can't see the exact build it went in on.
Can I get access to your cluster to look around to see if I missed something? It should be fixed.
I ping'ed you on slack, let me know if there is a way to test the same scenario you did.
I have validated this bugzilla on
Browser: Google Chrome Version 78.0.3904.108
@firstname.lastname@example.org provided some steps to validate this bug.
I followed the following steps to validate this bug:
1. Create a Pipeline
2. Manually CLI upload a Pipeline Run with a ‘spec.serviceAccount’ property equal to something
3. Upgrade to Pipeline Operator 0.9.0
4. From the UI, re-run the Pipeline Run that was uploaded
@email@example.com @firstname.lastname@example.org @email@example.com
Marking this bug as 'Release Pending'
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.