Bug 2065519
Summary: | Latest ose-jenkins:v4.8.0 image fails to display the Jenkins console in OpenShift 4.8 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | jamieclinton |
Component: | Jenkins | Assignee: | Adam Kaplan <adam.kaplan> |
Status: | CLOSED DUPLICATE | QA Contact: | Jitendar Singh <jitsingh> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.8 | CC: | adam.kaplan, aos-bugs, gmontero, pbhattac, spandura |
Target Milestone: | --- | ||
Target Release: | 4.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-04-12 14:49:31 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
jamieclinton
2022-03-18 03:18:42 UTC
Can you try using the ocp-tools-4 Jenkins image? We are test-driving a new version of Jenkins that is meant to work with all supported OpenShift versions. https://catalog.redhat.com/software/containers/ocp-tools-4/jenkins-rhel8/5fe1f38288e9c2f788526306 The problem we've been having with deploying the latest ose-jenkins:v4.8.0 image (also v4.9.0 and v4.10.0) appears to be related to FIPS, since we have a FIPS-enabled OpenShift cluster. I can get it to come up cleanly by adding the following variable to JAVA_TOOL_OPTIONS in our template: -Dcom.redhat.fips=false. As soon as I remove that variable from the template, it fails with errors similar to what I originally posted above. As for the ocp-tools-4 Jenkins image, I haven't tried it yet, but it only has a "B" security health index, so I'd rather stick with the latest ose-jenkins image, which has an "A" health index. my fix for https://bugzilla.redhat.com/show_bug.cgi?id=2066019 address both the core jenkins and agent image for the FIPs situation, so we can close this BZ as a dupe of that. Once QE starts verifies, we can start backporting. While the 4.11 version won't be available until 4.11 GAs in a couple of months, the 4.10 version of the fix, once merged, would be available at the next 4.10 errata. Looking at the container catalog for ocp-tools-4 imge I do not think the latest errata that has the necessary fixes has been posted yet (the last tag update is still March 22). I just pulled it and brought it up and confirmed it does not have Akram's fixes which we have verified internally. So I would hold off on that for now. *** This bug has been marked as a duplicate of bug 2066019 *** |