Bug 1726326
| Summary: | Jenkins sync plugin tests fail after cri-o bump | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | David Eads <deads> |
| Component: | Containers | Assignee: | Mrunal Patel <mpatel> |
| Status: | CLOSED ERRATA | QA Contact: | weiwei jiang <wjiang> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.0 | CC: | adam.kaplan, aos-bugs, bparees, chancez, dwalsh, jokerman, lsm5, mmccomas, nagrawal, wzheng |
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cri-o-1.14.6-1.rhaos4.2.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-16 06:32:48 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
David Eads
2019-07-02 15:35:15 UTC
Temporarily disabling sync plugin tests: https://github.com/openshift/origin/pull/23313 PR should be reverted once root cause is fixed. Assigning to Akram. Root cause of the issue is that the Java `user.home` system property is returning empty instead of $HOME or $JENKINS_HOME. As a result the Jenkins jar cache is attempting to write to `/.jenkins/cache`, which is prohibited. It's unclear why this changed - potential culprit is that cri-o was updated with https://openshift-release.svc.ci.openshift.org/releasestream/4.2.0-0.ci/release/4.2.0-0.ci-2019-07-02-021952 Potential root cause - cri-o not generating username and homedir to /etc/passwd. PR to address: https://github.com/cri-o/cri-o/pull/2563 Moving to Containers component. @Mrunal - when fix is added to OpenShift please ping the DevEx team, as we will need to re-enable the Jenkins sync plugin tests. Need wait nightly payload with cri-o-1.14.6. currently 4.2.0-0.nightly-2019-07-01-102521 is still crio-1.13.9 Checked with 4.2.0-0.nightly-2019-07-16-173254, and it's already on cri-o://1.14.6-1.rhaos4.2.el8. And this issue has been fixed now. 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-2019:2922 |