OAuth should log in current user into Jenkins. When creating a new project and adding a Jenkins Pipeline. We are not able to login current OpenShift user.
Users cannot log into Jenkins and Kibana using the Oauth.
Master nodes have 15.3Gb of RAM so it is not the minimum requirement, but this should not be the root cause.
"We are not able to login current OpenShift user" why? When? What error do you see? What have you done to troubleshoot it? Don't make me do the investigation you (hopefully) did for the second time.
If you have further information on the current state of the bug, please update it, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Hello, yes we can still see this error with the customer:
1. Warning: ServiceAccount 'jenkins-operator' not found
- Seem we are not using the jenkins operator.
2. Create new project jenkins-test
- I'm adding jenkins from the catalog
- Call the URL
- Log in with Openshift
- Asked for "Authorize Access" ...
- javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
I really can't tell what's going on from the provided description, then again, my knowledge of how Jenkins gets deployed in OpenShift equals zero. Perhaps people of the Jenkins component will know.
Can we have more information on this bug ?
mkdir bug-1852429 && cd bug-1852429
for plugin in `oc exec $JENKINS_POD_NAME ls /var/lib/jenkins/plugins -n $JENKINS_NAMESPACE | grep -v '.jpi'`;
do mkdir -p ./$plugin/META-INF;
oc cp $JENKINS_POD_NAME:/var/lib/jenkins/plugins/$plugin/META-INF ./$plugin/META-INF -n $JENKINS_NAMESPACE;
echo "copied $plugin"
The above will create a bug-1852429 dir which can be archived. Do send it to us.
oc exec $JENKINS_POD_NAME cat /var/lib/jenkins/config.xml | grep version
Also please provide output for the command above.
<?xml version='1.1' encoding='UTF-8'?>
Jenkins pod doesnt come up.
Do we have any information that I may share with the customer according to this Bugzilla?
I expect that it was dropped from the advisory RHSA-2020:4264 because some tests failed.
While OCP v4.3 is not supported I am not sure if the same issue is in newer versions of OCP.
@jawed can you please look into this.