Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1868250

Summary: Jenkins pod can't be running with error "Invalid configuration: '/var/lib/jenkins/proxy.yaml' "
Product: OpenShift Container Platform Reporter: XiuJuan Wang <xiuwang>
Component: JenkinsAssignee: Akram Ben Aissi <abenaiss>
Status: CLOSED DUPLICATE QA Contact: Jitendar Singh <jitsingh>
Severity: high Docs Contact:
Priority: high    
Version: 4.6CC: aos-bugs, pbhattac, vbobade
Target Milestone: ---   
Target Release: ---   
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: 2020-08-12 06:44:56 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 XiuJuan Wang 2020-08-12 06:35:41 UTC 
Description of problem:

Jenkins pod can't be running with error "Invalid configuration: '/var/lib/jenkins/proxy.yaml' "

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-08-11-165822

How reproducible:
always

Steps to Reproduce:
1.Create a jenkins server
$oc new-app jenkins-ephemeral
2.
3.

Actual results:
$ oc get pods  
NAME               READY   STATUS    RESTARTS   AGE
jenkins-1-deploy   0/1     Error     0          3h18m
jenkins-2-deploy   0/1     Error     0          164m
jenkins-3-6rszq    0/1     Running   0          6m30s
jenkins-3-deploy   1/1     Running   0          6m32s


2020-08-12 06:02:25 SEVERE  jenkins.InitReactorRunner$1 onTaskFailed Failed ConfigurationAsCode.init
java.lang.Error: java.lang.reflect.InvocationTargetException
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110)
	at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
	at jenkins.model.Jenkins$5.runTask(Jenkins.java:1131)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)
	... 9 more
Caused by: io.jenkins.plugins.casc.ConfiguratorException: Invalid configuration: '/var/lib/jenkins/proxy.yaml' isn't a valid path.
	at io.jenkins.plugins.casc.ConfigurationAsCode.configs(ConfigurationAsCode.java:643)
	at io.jenkins.plugins.casc.ConfigurationAsCode.appendSources(ConfigurationAsCode.java:263)
	at io.jenkins.plugins.casc.ConfigurationAsCode.getStandardConfigSources(ConfigurationAsCode.java:306)
	at io.jenkins.plugins.casc.ConfigurationAsCode.configure(ConfigurationAsCode.java:298)
	at io.jenkins.plugins.casc.ConfigurationAsCode.init(ConfigurationAsCode.java:290)

Expected results:
Jenkins pod could be running

Additional info:
Comment 1 Jitendar Singh 2020-08-12 06:43:36 UTC 
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1868069

@xiujuan - you can mark this as duplicate.
Comment 2 Jitendar Singh 2020-08-12 06:44:56 UTC 

*** This bug has been marked as a duplicate of bug 1868069 ***