[JIRA] (JENKINS-59775) Support Core dynamic loading is failing to load Master Log Record component

27 views
Skip to first unread message

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 14, 2019, 7:49:02 AM10/14/19
to jenkinsc...@googlegroups.com
Allan BURDAJEWICZ assigned an issue to Unassigned
 
Jenkins / Bug JENKINS-59775
Support Core dynamic loading is failing to load Master Log Record component
Change By: Allan BURDAJEWICZ
Assignee: Emilio  Escobar
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 14, 2019, 7:49:04 AM10/14/19
to jenkinsc...@googlegroups.com
Allan BURDAJEWICZ created an issue
Issue Type: Bug Bug
Assignee: Emilio Escobar
Components: support-core-plugin
Created: 2019-10-14 11:48
Environment: core:2.199
Priority: Minor Minor
Reporter: Allan BURDAJEWICZ

Installing support-core 2.62 fails to dynamically load one extension with the following warning being reported:

2019-10-14 11:03:04.794+0000 [id=100]	WARNING	h.ExtensionFinder$GuiceFinder$FaultTolerantScope$1#error: Failed to instantiate Key[type=com.cloudbees.jenkins.support.impl.JenkinsLogs, annotation=[none]]; skipping this component
hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
	at hudson.security.ACL.checkPermission(ACL.java:73)
	at hudson.security.AccessControlled.checkPermission(AccessControlled.java:47)
	at jenkins.model.Jenkins.getLog(Jenkins.java:2508)
	at com.cloudbees.jenkins.support.impl.JenkinsLogs.<init>(JenkinsLogs.java:50)
	at com.cloudbees.jenkins.support.impl.JenkinsLogs$$FastClassByGuice$$adeef6a3.newInstance(<generated>)
	at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
	at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
	at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
	at com.google.inject.internal.ConstructorInjector.access$000(ConstructorInjector.java:32)
	at com.google.inject.internal.ConstructorInjector$1.call(ConstructorInjector.java:89)
	at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
	at hudson.ExtensionFinder$GuiceFinder$SezpozModule.onProvision(ExtensionFinder.java:567)
	at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126)
	at hudson.ExtensionFinder$GuiceFinder$SezpozModule.onProvision(ExtensionFinder.java:567)
	at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126)
	at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
	at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:87)
	at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267)
	at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
	at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)
	at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
Caused: com.google.inject.ProvisionException: Unable to provision, see the following errors:

1) Error injecting constructor, hudson.security.AccessDeniedException2: anonymous is missing the Overall/Administer permission
  at com.cloudbees.jenkins.support.impl.JenkinsLogs.<init>(JenkinsLogs.java:46)

1 error
	at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
	at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)
	at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439)
	at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
	at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
	at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
	at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
	at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401)
	at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392)
	at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344)
	at hudson.ExtensionList.load(ExtensionList.java:381)
	at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317)
	at hudson.ExtensionList.iterator(ExtensionList.java:172)
	at com.cloudbees.jenkins.support.SupportPlugin.postInitialize(SupportPlugin.java:593)
	at hudson.PluginManager.start(PluginManager.java:954)
	at hudson.model.UpdateCenter$CompleteBatchJob.run(UpdateCenter.java:2175)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:111)
	at java.lang.Thread.run(Thread.java:748)

Which causes the "Master Log Recorder" component to not be available in the Support action.

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 14, 2019, 7:50:02 AM10/14/19
to jenkinsc...@googlegroups.com

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 23, 2019, 2:32:03 AM10/23/19
to jenkinsc...@googlegroups.com

Seems related to the the install of plugins in batch. Seems like the CompleteBatchJob runs in a thread without impersonation.

Jesse Glick Is this actually a bug in core, where CompleteBatchJob should impersonate SYSTEM ?

jglick@cloudbees.com (JIRA)

unread,
Oct 23, 2019, 4:46:02 PM10/23/19
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Oct 23, 2019, 4:49:02 PM10/23/19
to jenkinsc...@googlegroups.com

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 24, 2019, 7:16:05 PM10/24/19
to jenkinsc...@googlegroups.com

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 24, 2019, 11:50:04 PM10/24/19
to jenkinsc...@googlegroups.com

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 24, 2019, 11:50:05 PM10/24/19
to jenkinsc...@googlegroups.com
Allan BURDAJEWICZ started work on Bug JENKINS-59775
 
Change By: Allan BURDAJEWICZ
Status: Open In Progress

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 24, 2019, 11:57:03 PM10/24/19
to jenkinsc...@googlegroups.com

aburdajewicz@cloudbees.com (JIRA)

unread,
Oct 24, 2019, 11:57:03 PM10/24/19
to jenkinsc...@googlegroups.com

jglick@cloudbees.com (JIRA)

unread,
Oct 25, 2019, 8:50:03 AM10/25/19
to jenkinsc...@googlegroups.com
 
Re: Support Core dynamic loading is failing to load Master Log Record component

Is this confirmed to be a regression? If so, please add the regression label.

dbeck@cloudbees.com (JIRA)

unread,
Oct 31, 2019, 3:00:03 AM10/31/19
to jenkinsc...@googlegroups.com

Occurs on 2.190.x, I saw this happen on ci.jenkins.io while it still had the support-core plugin (and another reason I lost confidence in it).

aburdajewicz@cloudbees.com (JIRA)

unread,
Nov 3, 2019, 6:42:03 PM11/3/19
to jenkinsc...@googlegroups.com

aburdajewicz@cloudbees.com (JIRA)

unread,
Nov 3, 2019, 6:43:02 PM11/3/19
to jenkinsc...@googlegroups.com

aheritier@apache.org (JIRA)

unread,
Nov 6, 2019, 4:50:02 AM11/6/19
to jenkinsc...@googlegroups.com
Arnaud Héritier commented on Bug JENKINS-59775
 
Re: Support Core dynamic loading is failing to load Master Log Record component

I confirm that it's a problem with 2.190.x (reproduced today. No logs in the bundle until your restart (ref JENKINS-60073 to close as duplicated if confirmed)

aburdajewicz@cloudbees.com (JIRA)

unread,
Nov 8, 2019, 2:45:02 AM11/8/19
to jenkinsc...@googlegroups.com

aburdajewicz@cloudbees.com (JIRA)

unread,
Nov 8, 2019, 2:46:03 AM11/8/19
to jenkinsc...@googlegroups.com

dbeck@cloudbees.com (JIRA)

unread,
Nov 22, 2019, 6:16:08 AM11/22/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages