Bug 1532936
| Summary: | Cannot add env vars into slave pod template in jenkins webconsole against jenkins-2-rhel7 image | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dongbo Yan <dyan> |
| Component: | ImageStreams | Assignee: | Gabe Montero <gmontero> |
| Status: | CLOSED ERRATA | QA Contact: | Dongbo Yan <dyan> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.9.0 | CC: | aos-bugs, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: There was a bug in the kubernetes plugin from upstream jenkins that did not allow the adding of env vars to pod templates unless env vars were defined at the global jenkins level.
Consequence: Adding pod template env vars were cumbersome.
Fix: An upstream jenkins kubernetes plugin fix arrived, and it was pulled into the openshift jenkins image.
Result: You can now add env vars to templates from the jenkins console regardless of what env vars were previously defined.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-28 14:18:26 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
Dongbo Yan
2018-01-10 02:59:33 UTC
I think we may have had this reported before and the issue is that you need to define the env var as a jenkins env var before you can add it to the pod template, but not sure. Gabe should be able to confirm. (It is certainly strange if you have to define the env var in jenkins to add it via the console, but can explicitly configure arbitrary env vars when doing it via the xml). Dongbo Yan's timing is spot on :-) As was Ben's recollection on the item and the workaround Turns out, the k8s plugin is now tracking this via https://issues.jenkins-ci.org/browse/JENKINS-47112 and the repo owner just noted earlier today that the fix is in the v1.1.3 he just published earlier today. We are currently at 1.0.0, and would pick up about another dozen fixes in addition to this one. Ben - and I'll preface that I am on the fence here - what is your take on the risk/reward with updating the k8s plugin version with dcut later today? Created https://github.com/openshift/jenkins/pull/475 to track. Running a plugin regression. OK PR has merged and https://buildvm.openshift.eng.bos.redhat.com:8443/job/devex/job/devex%252Fjenkins-plugins/20/ has completed. Moving to on qa for them to try with centos image when it arrives on docker hub or rhel image when it arrives in appropriate staging area. associated dist-git: http://pkgs.devel.redhat.com/cgit/rpms/jenkins-2-plugins/?h=rhaos-3.9-rhel-7 Verified with docker.io/openshift/jenkins-2-centos7 (6d8d0127a29e) kubernetes 1.1.3 could add env vars into pod template in jenkins webconsole. when new rhel image built, will test again. move this bug to modified Test with brew-pulp.../openshift3/jenkins-2-rhel7 (0c405904a82a) cannot reproduce this issue, could move to verified 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:0489 |