Bug 1155766
Summary: | Moving the application with jenkins client make the project be changed to disabled in jenkins server console | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
Component: | ImageStreams | Assignee: | Jason DeTiberus <jdetiber> |
Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.2.0 | CC: | adellape, bparees, decarr, gpei, jokerman, libra-bugs, libra-onpremise-devel, mfojtik, mmahut, mmccomas, pruan, wsun |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | openshift-origin-cartridge-jenkins-1.26.1.1-1 | Doc Type: | Bug Fix |
Doc Text: |
If a gear hosting the git repository for an application moves to another node, subsequent Jenkins clones will fail. This was due to the Jenkins git SSH wrapper checking Known Hosts. This bug fix updates the related call to remove Known Host checking. Other security methods built in to git provide sufficient protection against tampering. As a result, gears can now be moved freely and Jenkins builds are able to be triggered successfully. After applying this update, a cartridge upgrade is required.
|
Story Points: | --- |
Clone Of: | 1153557 | Environment: | |
Last Closed: | 2014-12-10 13:24:38 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: | |||
Bug Depends On: | 1153557 | ||
Bug Blocks: |
Description
Brenton Leanhardt
2014-10-22 18:43:07 UTC
Verify this bug on puddle 2.2/2014-11-24.3 with mod-rewrite frontend. After move the application to another node within the same district, jenkins build could be trigger successfully. Both scalable and non-scalable app work well. 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://rhn.redhat.com/errata/RHBA-2014-1979.html |