Bug 1789119
| Summary: | Support Pipeline Operator 0.9.0 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Andrew Ballantyne <aballant> | ||||||
| Component: | Dev Console | Assignee: | Andrew Ballantyne <aballant> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.3.0 | CC: | aos-bugs, cvogt, eparis, nmukherj, rgarg | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 4.2.z | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | 1788201 | Environment: | |||||||
| Last Closed: | 2020-01-22 10:46:40 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | 1778958 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1652427 [details]
Latest 4.2 CI build
@aballant @hasha 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. @gamore 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 Build:4.2.0-0.nightly-2020-01-15-231532 Browser: Google Chrome Version 78.0.3904.108 @aballant 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 @aballant @hasha @rgarg 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. https://access.redhat.com/errata/RHBA-2020:0107 |
Created attachment 1652426 [details] 4.2 stable