Bug 1396022
Summary: | The parameter "namespace" is mandatory in "Run OpenShift Exec" dsl step | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Dongbo Yan <dyan> |
Component: | ImageStreams | Assignee: | Justin Pierce <jupierce> |
Status: | CLOSED ERRATA | QA Contact: | Wang Haoran <haowang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.4.0 | CC: | aos-bugs, bparees, dyan, jokerman, mmccomas, tdawson |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
Failure to use overrides methods in one area of Jenkins plugin exec implementation.
Consequence:
Fix:
https://github.com/openshift/jenkins-plugin/pull/115
Result:
Namespace is now an optional parameter.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-01-18 12:55:36 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
2016-11-17 09:22:23 UTC
Fix in progress: https://github.com/openshift/jenkins-plugin/pull/115 Should be fixed in rpm jenkins-plugin-openshift-pipeline-1.0.35-1.el7 and images: openshift3/jenkins-1-rhel7:1.651.2-35 openshift3/jenkins-2-rhel7:2.7-20 @Dongbo it's not clear why this failedqa? Was it because of https://bugzilla.redhat.com/show_bug.cgi?id=1396918 preventing things from working? I should change to modified, not failedQA. Due to plugin cannot load in jenkins server with the image Test with brew-pulp.../openshift3/jenkins-1-rhel7 latest 9edb7f9e5157 brew-pulp.../openshift3/jenkins-2-rhel7 latest b5b09fbedfc0 openshift-login 0.9 openshift-pipeline 1.0.36 openshift-sync 0.0.17 openshift v3.4.0.28+dfe3a66 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 jenkins job success 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-2017:0066 |