Bug 1565894
| Summary: | Jenkins job is delayed to delete for about 1 minute after removing pipeline build in openshift | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | wewang <wewang> |
| Component: | Build | Assignee: | Corey Daley <cdaley> |
| Status: | CLOSED ERRATA | QA Contact: | wewang <wewang> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.10.0 | CC: | aos-bugs, bparees |
| Target Milestone: | --- | ||
| Target Release: | 3.10.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-07-30 19:12:35 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
wewang
2018-04-11 02:12:04 UTC
Ben/Gabe, Once the run reaches the onComplete or onFinalized section of the code it is removed from the runsToPoll list and is essentially ignored until the run gets deleted by the reconciler. This was the existing logic and why runs were stacking up and not being removed at all when builds were deleted from OpenShift. Is the desired behavior that the BuildSyncRunListener should check every 5 seconds for deleted builds and remove the associated job runs? Submitted pull request https://github.com/openshift/jenkins-sync-plugin/pull/224 Pull request has been merged @Corey Daley could you move status to ON_QA,so I can verify it verified in Version-Release number of selected component (if applicable): brew-pulp-xxxxxx/openshift3/jenkins-2-rhel7 v3.10 ac1e304de673 sync plugin v1.0.14 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-2018:1816 |