[JENKINS-71966] Blue ocean and kubernetes stack trace with Jenkins 2.387.3 and snakeyaml 2.2

Type: Bug
Resolution: Won't Fix
Priority: Minor
Component/s: blueocean-plugin, kubernetes-plugin, snakeyaml-plugin
Labels:
None
Environment:

Hide
Jenkins 2.387.3
Java 11.0.20.1

ant:497.v94e7d9fffa_b_9
antisamy-markup-formatter:162.v0e6ec0fcfcf6
apache-httpcomponents-client-4-api:4.5.14-208.v438351942757
authentication-tokens:1.53.v1c90fd9191a_b_
blueocean:1.27.5.1
blueocean-bitbucket-pipeline:1.27.5.1
blueocean-commons:1.27.5.1
blueocean-config:1.27.5.1
blueocean-core-js:1.27.5.1
blueocean-dashboard:1.27.5.1
blueocean-display-url:2.4.2
blueocean-events:1.27.5.1
blueocean-git-pipeline:1.27.5.1
blueocean-github-pipeline:1.27.5.1
blueocean-i18n:1.27.5.1
blueocean-jwt:1.27.5.1
blueocean-personalization:1.27.5.1
blueocean-pipeline-api-impl:1.27.5.1
blueocean-pipeline-editor:1.27.5.1
blueocean-pipeline-scm-api:1.27.5.1
blueocean-rest:1.27.5.1
blueocean-rest-impl:1.27.5.1
blueocean-web:1.27.5.1
bootstrap5-api:5.3.0-1
bouncycastle-api:2.29
branch-api:2.1122.v09cb_8ea_8a_724
build-timeout:1.31
caffeine-api:3.1.8-133.v17b_1ff2e0599
checks-api:2.0.0
cloudbees-bitbucket-branch-source:832.v43175a_425ea_6
cloudbees-folder:6.848.ve3b_fd7839a_81
commons-lang3-api:3.13.0-62.v7d18e55f51e2
commons-text-api:1.10.0-78.v3e7b_ea_d5a_fe1
credentials:1271.v54b_1c2c6388a_
credentials-binding:631.v861c06d062b_4
display-url-api:2.3.9
durable-task:523.va_a_22cf15d5e0
echarts-api:5.4.0-5
email-ext:2.100
favorite:2.4.3
font-awesome-api:6.4.0-2
git:5.2.0
git-client:4.4.0
github:1.37.3
github-api:1.314-431.v78d72a_3fe4c3
github-branch-source:1732.v3f1889a_c475b_
gradle:2.8.2
handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953
htmlpublisher:1.32
instance-identity:173.va_37c494ec4e5
ionicons-api:56.v1b_1c8c49374e
jackson2-api:2.15.2-350.v0c2f3f8fc595
jakarta-activation-api:2.0.1-3
jakarta-mail-api:2.0.1-3
javax-activation-api:1.2.0-6
javax-mail-api:1.6.2-9
jaxb:2.3.8-1
jenkins-design-language:1.27.5.1
jjwt-api:0.11.5-77.v646c772fddb_0
jquery3-api:3.7.0-1
junit:1217.v4297208a_a_b_ce
ldap:694.vc02a_69c9787f
mailer:463.vedf8358e006b_
matrix-auth:3.2
matrix-project:808.v5a_b_5f56d6966
mina-sshd-api-common:2.10.0-69.v28e3e36d18eb_
mina-sshd-api-core:2.10.0-69.v28e3e36d18eb_
okhttp-api:4.11.0-157.v6852a_a_fa_ec11
pam-auth:1.10
pipeline-build-step:505.v5f0844d8d126
pipeline-github-lib:42.v0739460cda_c4
pipeline-graph-analysis:202.va_d268e64deb_3
pipeline-groovy-lib:685.v8ee9ed91d574
pipeline-input-step:477.v339683a_8d55e
pipeline-milestone-step:111.v449306f708b_7
pipeline-model-api:2.2144.v077a_d1928a_40
pipeline-model-definition:2.2144.v077a_d1928a_40
pipeline-model-extensions:2.2144.v077a_d1928a_40
pipeline-rest-api:2.33
pipeline-stage-step:305.ve96d0205c1c6
pipeline-stage-tags-metadata:2.2144.v077a_d1928a_40
pipeline-stage-view:2.33
plain-credentials:143.v1b_df8b_d3b_e48
plugin-util-api:3.3.0
pubsub-light:1.17
resource-disposer:0.23
scm-api:676.v886669a_199a_a_
script-security:1275.v23895f409fb_d
snakeyaml-api:2.2-111.vc6598e30cc65
sse-gateway:1.26
ssh-credentials:308.ve4497b_ccd8f4
ssh-slaves:2.916.vd17b_43357ce4
structs:325.vcb_307d2a_2782
timestamper:1.26
token-macro:384.vf35b_f26814ec
trilead-api:2.84.v72119de229b_7
variant:60.v7290fc0eb_b_cd
workflow-aggregator:596.v8c21c963d92d
workflow-api:1267.vd9b_a_ddd9eb_47
workflow-basic-steps:1042.ve7b_140c4a_e0c
workflow-cps:3774.v4a_d648d409ce
workflow-durable-task-step:1289.v4d3e7b_01546b_
workflow-job:1326.ve643e00e9220
workflow-multibranch:756.v891d88f2cd46
workflow-scm-step:415.v434365564324
workflow-step-api:639.v6eca_cd8c04a_a_
workflow-support:848.v5a_383b_d14921
ws-cleanup:0.45

Show
Jenkins 2.387.3 Java 11.0.20.1 ant:497.v94e7d9fffa_b_9 antisamy-markup-formatter:162.v0e6ec0fcfcf6 apache-httpcomponents-client-4-api:4.5.14-208.v438351942757 authentication-tokens:1.53.v1c90fd9191a_b_ blueocean:1.27.5.1 blueocean-bitbucket-pipeline:1.27.5.1 blueocean-commons:1.27.5.1 blueocean-config:1.27.5.1 blueocean-core-js:1.27.5.1 blueocean-dashboard:1.27.5.1 blueocean-display-url:2.4.2 blueocean-events:1.27.5.1 blueocean-git-pipeline:1.27.5.1 blueocean-github-pipeline:1.27.5.1 blueocean-i18n:1.27.5.1 blueocean-jwt:1.27.5.1 blueocean-personalization:1.27.5.1 blueocean-pipeline-api-impl:1.27.5.1 blueocean-pipeline-editor:1.27.5.1 blueocean-pipeline-scm-api:1.27.5.1 blueocean-rest:1.27.5.1 blueocean-rest-impl:1.27.5.1 blueocean-web:1.27.5.1 bootstrap5-api:5.3.0-1 bouncycastle-api:2.29 branch-api:2.1122.v09cb_8ea_8a_724 build-timeout:1.31 caffeine-api:3.1.8-133.v17b_1ff2e0599 checks-api:2.0.0 cloudbees-bitbucket-branch-source:832.v43175a_425ea_6 cloudbees-folder:6.848.ve3b_fd7839a_81 commons-lang3-api:3.13.0-62.v7d18e55f51e2 commons-text-api:1.10.0-78.v3e7b_ea_d5a_fe1 credentials:1271.v54b_1c2c6388a_ credentials-binding:631.v861c06d062b_4 display-url-api:2.3.9 durable-task:523.va_a_22cf15d5e0 echarts-api:5.4.0-5 email-ext:2.100 favorite:2.4.3 font-awesome-api:6.4.0-2 git:5.2.0 git-client:4.4.0 github:1.37.3 github-api:1.314-431.v78d72a_3fe4c3 github-branch-source:1732.v3f1889a_c475b_ gradle:2.8.2 handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953 htmlpublisher:1.32 instance-identity:173.va_37c494ec4e5 ionicons-api:56.v1b_1c8c49374e jackson2-api:2.15.2-350.v0c2f3f8fc595 jakarta-activation-api:2.0.1-3 jakarta-mail-api:2.0.1-3 javax-activation-api:1.2.0-6 javax-mail-api:1.6.2-9 jaxb:2.3.8-1 jenkins-design-language:1.27.5.1 jjwt-api:0.11.5-77.v646c772fddb_0 jquery3-api:3.7.0-1 junit:1217.v4297208a_a_b_ce ldap:694.vc02a_69c9787f mailer:463.vedf8358e006b_ matrix-auth:3.2 matrix-project:808.v5a_b_5f56d6966 mina-sshd-api-common:2.10.0-69.v28e3e36d18eb_ mina-sshd-api-core:2.10.0-69.v28e3e36d18eb_ okhttp-api:4.11.0-157.v6852a_a_fa_ec11 pam-auth:1.10 pipeline-build-step:505.v5f0844d8d126 pipeline-github-lib:42.v0739460cda_c4 pipeline-graph-analysis:202.va_d268e64deb_3 pipeline-groovy-lib:685.v8ee9ed91d574 pipeline-input-step:477.v339683a_8d55e pipeline-milestone-step:111.v449306f708b_7 pipeline-model-api:2.2144.v077a_d1928a_40 pipeline-model-definition:2.2144.v077a_d1928a_40 pipeline-model-extensions:2.2144.v077a_d1928a_40 pipeline-rest-api:2.33 pipeline-stage-step:305.ve96d0205c1c6 pipeline-stage-tags-metadata:2.2144.v077a_d1928a_40 pipeline-stage-view:2.33 plain-credentials:143.v1b_df8b_d3b_e48 plugin-util-api:3.3.0 pubsub-light:1.17 resource-disposer:0.23 scm-api:676.v886669a_199a_a_ script-security:1275.v23895f409fb_d snakeyaml-api:2.2-111.vc6598e30cc65 sse-gateway:1.26 ssh-credentials:308.ve4497b_ccd8f4 ssh-slaves:2.916.vd17b_43357ce4 structs:325.vcb_307d2a_2782 timestamper:1.26 token-macro:384.vf35b_f26814ec trilead-api:2.84.v72119de229b_7 variant:60.v7290fc0eb_b_cd workflow-aggregator:596.v8c21c963d92d workflow-api:1267.vd9b_a_ddd9eb_47 workflow-basic-steps:1042.ve7b_140c4a_e0c workflow-cps:3774.v4a_d648d409ce workflow-durable-task-step:1289.v4d3e7b_01546b_ workflow-job:1326.ve643e00e9220 workflow-multibranch:756.v891d88f2cd46 workflow-scm-step:415.v434365564324 workflow-step-api:639.v6eca_cd8c04a_a_ workflow-support:848.v5a_383b_d14921 ws-cleanup:0.45

Similar Issues:
Powered by SuggestiMate

Show

When I install the suggested plugins from the Jenkins 2.387.3 setup wizard and then install the blue ocean plugin, Jenkins reports a stack trace on startup. The stack trace is:

2023-09-05 00:56:56.020+0000 [id=35]    WARNING hudson.ExtensionFinder$Sezpoz#scout: Failed to scout io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties
java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor: method 'void <init>()' not found
        at ua_parser.Parser.initialize(Parser.java:80)
        at ua_parser.Parser.<init>(Parser.java:45)
        at io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties.<clinit>(BrowserAndOperatingSystemAnalyticsProperties.java:19)
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:398)
        at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:769)
        at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353)
        at hudson.ExtensionList.load(ExtensionList.java:384)
        at hudson.ExtensionList.ensureLoaded(ExtensionList.java:320)
        at hudson.ExtensionList.getComponents(ExtensionList.java:184)
        at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1196)
        at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:88)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:116)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:182)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        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:829)

A stack trace is expected from the kubernetes 4007.v633279962016 plugin when installed with Jenkins 2.387.3 and snakeyaml api plugin 2.2-111.vc6598e30cc65. I've not been able to create a scenario with the kubernetes plugin, but the automated tests show the following stack trace:

java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor: method 'void <init>()' not found
	at io.fabric8.kubernetes.client.utils.Serialization.unmarshal(Serialization.java:256)
	at io.fabric8.kubernetes.client.utils.Serialization.unmarshal(Serialization.java:387)
	at io.fabric8.kubernetes.client.utils.Serialization.unmarshal(Serialization.java:353)
	at io.fabric8.kubernetes.client.utils.Serialization.unmarshal(Serialization.java:337)
	at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.unmarshal(OperationSupport.java:753)
	at io.fabric8.kubernetes.client.dsl.internal.BaseOperation.load(BaseOperation.java:261)
	at io.fabric8.kubernetes.client.dsl.internal.BaseOperation.load(BaseOperation.java:93)
	at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.parseFromYaml(PodTemplateUtils.java:610)
	at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
	at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
	at org.csanchez.jenkins.plugins.kubernetes.pod.yaml.Merge.merge(Merge.java:25)
	at org.csanchez.jenkins.plugins.kubernetes.PodTemplate.getYamlsPod(PodTemplate.java:201)
	at org.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder.build(PodTemplateBuilder.java:297)
	at org.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilderTest.yamlOverrideSecurityContext(PodTemplateBuilderTest.java:817)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.mockito.internal.junit.JUnitSessionStore$1.evaluateSafely(JUnitSessionStore.java:55)
	at org.mockito.internal.junit.JUnitSessionStore$1.evaluate(JUnitSessionStore.java:43)
	at org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:607)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.lang.Thread.run(Thread.java:829)

Workarounds

The issue can be avoided by choosing to not upgrade the snakeyaml plugin to 2.2.

The issue can also be avoided by upgrading from Jenkins 2.387.3 to Jenkins 2.401.3 or Jenkins 2.414.1 and upgrading the blue ocean plugins. An updated blue ocean plugin (1.27.6) is available for Jenkins 2.401.3 with support for snakeyaml 2.2

History

This failure was originally detected in the Jenkins plugin bill of materials as part of a full test.

Steps to duplicate the issue:

Create a plugins.txt with the list of plugin versions to be installed
Create a run-jenkins.sh shell script to download Jenkins 2.387.3 and the plugins
Run the run-jenkins.sh shell script
Complete the setup wizard by creating a user and choosing to install no additional plugins
Confirm that the stack trace is not visible in the Jenkins console output
Use the plugin manager page to upgrade the snakeyaml plugin to snakeyaml 2.2
Restart Jenkins and confirm that the stack trace is now reported as listed above

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

run-jenkins.sh
0.8 kB
2023-09-05 01:35
plugins.txt
3 kB
2023-09-05 01:34

is duplicated by

JENKINS-72545 pod scheduling fails with `method 'void <init>()' not found ` installed oidc plugin and that upgraded snakeYaml plugin from 1.33 to 2.2-111.vc6598e30cc65

Closed

links to

SnakeYAML API plugin 2.2 release notes

Mark Waite created issue - 2023-09-05 01:04

Mark Waite made changes - 2023-09-05 01:32

Description

Original: When I install the suggested plugins from the Jenkins 2.387.3 setup wizard and then install the blue ocean plugin, Jenkins reports a stack trace on startup. The stack trace is:

{noformat}
2023-09-05 00:56:56.020+0000 [id=35] WARNING hudson.ExtensionFinder$Sezpoz#scout: Failed to scout io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties
java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor: method 'void <init>()' not found
        at ua_parser.Parser.initialize(Parser.java:80)
        at ua_parser.Parser.<init>(Parser.java:45)
        at io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties.<clinit>(BrowserAndOperatingSystemAnalyticsProperties.java:19)
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:398)
        at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:769)
        at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353)
        at hudson.ExtensionList.load(ExtensionList.java:384)
        at hudson.ExtensionList.ensureLoaded(ExtensionList.java:320)
        at hudson.ExtensionList.getComponents(ExtensionList.java:184)
        at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1196)
        at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:88)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:116)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:182)
        at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        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:829)
{noformat}

I suspect that the issue can be avoided by choosing to not upgrade the snakeyaml plugin to 2.2.

New: When I install the suggested plugins from the Jenkins 2.387.3 setup wizard and then install the blue ocean plugin, Jenkins reports a stack trace on startup. The stack trace is:

{noformat}
2023-09-05 00:56:56.020+0000 [id=35] WARNING hudson.ExtensionFinder$Sezpoz#scout: Failed to scout io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties
java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor: method 'void <init>()' not found
        at ua_parser.Parser.initialize(Parser.java:80)
        at ua_parser.Parser.<init>(Parser.java:45)
        at io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties.<clinit>(BrowserAndOperatingSystemAnalyticsProperties.java:19)
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:398)
        at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:769)
        at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353)
        at hudson.ExtensionList.load(ExtensionList.java:384)
        at hudson.ExtensionList.ensureLoaded(ExtensionList.java:320)
        at hudson.ExtensionList.getComponents(ExtensionList.java:184)
        at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1196)
        at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:88)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:116)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:182)
        at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        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:829)
{noformat}

The issue can be avoided by choosing to not upgrade the snakeyaml plugin to 2.2.

The issue can also be avoided by upgrading from Jenkins 2.387.3 to Jenkins 2.401.3 or Jenkins 2.414.1 and upgrading the blue ocean plugins. An updated blue ocean plugin (1.27.6) is available for Jenkins 2.401.3 with support for snakeyaml 2.2

This failure was originally detected in the [Jenkins plugin bill of materials|https://github.com/jenkinsci/bom/pull/2464/checks?check_run_id=16489531836] as part of a full test.

Mark Waite made changes - 2023-09-05 01:34

Attachment

New: plugins.txt [ 61104 ]

Mark Waite made changes - 2023-09-05 01:35

Attachment

New: run-jenkins.sh [ 61105 ]

Mark Waite made changes - 2023-09-05 01:37

Description

Original: When I install the suggested plugins from the Jenkins 2.387.3 setup wizard and then install the blue ocean plugin, Jenkins reports a stack trace on startup. The stack trace is:

{noformat}
2023-09-05 00:56:56.020+0000 [id=35] WARNING hudson.ExtensionFinder$Sezpoz#scout: Failed to scout io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties
java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor: method 'void <init>()' not found
        at ua_parser.Parser.initialize(Parser.java:80)
        at ua_parser.Parser.<init>(Parser.java:45)
        at io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties.<clinit>(BrowserAndOperatingSystemAnalyticsProperties.java:19)
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:398)
        at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:769)
        at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353)
        at hudson.ExtensionList.load(ExtensionList.java:384)
        at hudson.ExtensionList.ensureLoaded(ExtensionList.java:320)
        at hudson.ExtensionList.getComponents(ExtensionList.java:184)
        at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1196)
        at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:88)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:116)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:182)
        at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        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:829)
{noformat}

The issue can be avoided by choosing to not upgrade the snakeyaml plugin to 2.2.

The issue can also be avoided by upgrading from Jenkins 2.387.3 to Jenkins 2.401.3 or Jenkins 2.414.1 and upgrading the blue ocean plugins. An updated blue ocean plugin (1.27.6) is available for Jenkins 2.401.3 with support for snakeyaml 2.2

This failure was originally detected in the [Jenkins plugin bill of materials|https://github.com/jenkinsci/bom/pull/2464/checks?check_run_id=16489531836] as part of a full test.

New: When I install the suggested plugins from the Jenkins 2.387.3 setup wizard and then install the blue ocean plugin, Jenkins reports a stack trace on startup. The stack trace is:

{noformat}
2023-09-05 00:56:56.020+0000 [id=35] WARNING hudson.ExtensionFinder$Sezpoz#scout: Failed to scout io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties
java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor: method 'void <init>()' not found
        at ua_parser.Parser.initialize(Parser.java:80)
        at ua_parser.Parser.<init>(Parser.java:45)
        at io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties.<clinit>(BrowserAndOperatingSystemAnalyticsProperties.java:19)
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:398)
        at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:769)
        at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353)
        at hudson.ExtensionList.load(ExtensionList.java:384)
        at hudson.ExtensionList.ensureLoaded(ExtensionList.java:320)
        at hudson.ExtensionList.getComponents(ExtensionList.java:184)
        at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1196)
        at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:88)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:116)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:182)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        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:829)
{noformat}

The issue can be avoided by choosing to not upgrade the snakeyaml plugin to 2.2.

The issue can also be avoided by upgrading from Jenkins 2.387.3 to Jenkins 2.401.3 or Jenkins 2.414.1 and upgrading the blue ocean plugins. An updated blue ocean plugin (1.27.6) is available for Jenkins 2.401.3 with support for snakeyaml 2.2

This failure was originally detected in the [Jenkins plugin bill of materials|https://github.com/jenkinsci/bom/pull/2464/checks?check_run_id=16489531836] as part of a full test.

Steps to duplicate the issue:

# Create a [^plugins.txt] with the list of plugin versions to be installed
# Create a [^run-jenkins.sh] shell script to download Jenkins 2.387.3 and the plugins
# Run the [^run-jenkins.sh] shell script
# Complete the setup wizard by creating a user and choosing to install no additional plugins
# Confirm that the stack trace is not visible in the Jenkins console output
# Use the plugin manager page to upgrade the snakeyaml plugin to snakeyaml 2.2
# Restart Jenkins and confirm that the stack trace is now reported as listed above

Mark Waite made changes - 2023-09-05 01:41

Description

Original: When I install the suggested plugins from the Jenkins 2.387.3 setup wizard and then install the blue ocean plugin, Jenkins reports a stack trace on startup. The stack trace is:

{noformat}
2023-09-05 00:56:56.020+0000 [id=35] WARNING hudson.ExtensionFinder$Sezpoz#scout: Failed to scout io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties
java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor: method 'void <init>()' not found
        at ua_parser.Parser.initialize(Parser.java:80)
        at ua_parser.Parser.<init>(Parser.java:45)
        at io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties.<clinit>(BrowserAndOperatingSystemAnalyticsProperties.java:19)
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:398)
        at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:769)
        at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353)
        at hudson.ExtensionList.load(ExtensionList.java:384)
        at hudson.ExtensionList.ensureLoaded(ExtensionList.java:320)
        at hudson.ExtensionList.getComponents(ExtensionList.java:184)
        at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1196)
        at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:88)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:116)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:182)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        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:829)
{noformat}

The issue can be avoided by choosing to not upgrade the snakeyaml plugin to 2.2.

The issue can also be avoided by upgrading from Jenkins 2.387.3 to Jenkins 2.401.3 or Jenkins 2.414.1 and upgrading the blue ocean plugins. An updated blue ocean plugin (1.27.6) is available for Jenkins 2.401.3 with support for snakeyaml 2.2

This failure was originally detected in the [Jenkins plugin bill of materials|https://github.com/jenkinsci/bom/pull/2464/checks?check_run_id=16489531836] as part of a full test.

Steps to duplicate the issue:

# Create a [^plugins.txt] with the list of plugin versions to be installed
# Create a [^run-jenkins.sh] shell script to download Jenkins 2.387.3 and the plugins
# Run the [^run-jenkins.sh] shell script
# Complete the setup wizard by creating a user and choosing to install no additional plugins
# Confirm that the stack trace is not visible in the Jenkins console output
# Use the plugin manager page to upgrade the snakeyaml plugin to snakeyaml 2.2
# Restart Jenkins and confirm that the stack trace is now reported as listed above

New: When I install the suggested plugins from the Jenkins 2.387.3 setup wizard and then install the blue ocean plugin, Jenkins reports a stack trace on startup. The stack trace is:

{noformat}
2023-09-05 00:56:56.020+0000 [id=35] WARNING hudson.ExtensionFinder$Sezpoz#scout: Failed to scout io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties
java.lang.NoSuchMethodError: org.yaml.snakeyaml.constructor.SafeConstructor: method 'void <init>()' not found
        at ua_parser.Parser.initialize(Parser.java:80)
        at ua_parser.Parser.<init>(Parser.java:45)
        at io.jenkins.blueocean.service.embedded.analytics.BrowserAndOperatingSystemAnalyticsProperties.<clinit>(BrowserAndOperatingSystemAnalyticsProperties.java:19)
        at java.base/java.lang.Class.forName0(Native Method)
        at java.base/java.lang.Class.forName(Class.java:398)
        at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:769)
        at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353)
        at hudson.ExtensionList.load(ExtensionList.java:384)
        at hudson.ExtensionList.ensureLoaded(ExtensionList.java:320)
        at hudson.ExtensionList.getComponents(ExtensionList.java:184)
        at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1196)
        at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:88)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.run(ReactorListener.java:116)
        at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:108)
        at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:182)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:120)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
        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:829)
{noformat}

h2. Workarounds

The issue can be avoided by choosing to not upgrade the snakeyaml plugin to 2.2.

The issue can also be avoided by upgrading from Jenkins 2.387.3 to Jenkins 2.401.3 or Jenkins 2.414.1 and upgrading the blue ocean plugins. An updated blue ocean plugin (1.27.6) is available for Jenkins 2.401.3 with support for snakeyaml 2.2

h2. History

This failure was originally detected in the [Jenkins plugin bill of materials|https://github.com/jenkinsci/bom/pull/2464/checks?check_run_id=16489531836] as part of a full test.

h2. Steps to duplicate the issue:

# Create a [^plugins.txt] with the list of plugin versions to be installed
# Create a [^run-jenkins.sh] shell script to download Jenkins 2.387.3 and the plugins
# Run the [^run-jenkins.sh] shell script
# Complete the setup wizard by creating a user and choosing to install no additional plugins
# Confirm that the stack trace is not visible in the Jenkins console output
# Use the plugin manager page to upgrade the snakeyaml plugin to snakeyaml 2.2
# Restart Jenkins and confirm that the stack trace is now reported as listed above

Mark Waite added a comment - 2023-09-05 01:59

olamy I assume it is intentional that the blue ocean plugins available with Jenkins 2.387.3 (and earlier) are not compatible with the snakeyaml 2.2 plugin. Users should upgrade to 2.414.1 (first preference) or 2.401.3 (second preference).

Mark Waite added a comment - 2023-09-05 01:59 olamy I assume it is intentional that the blue ocean plugins available with Jenkins 2.387.3 (and earlier) are not compatible with the snakeyaml 2.2 plugin. Users should upgrade to 2.414.1 (first preference) or 2.401.3 (second preference).

Olivier Lamy added a comment - 2023-09-05 02:10

I wouldn't say intentional but the fix for snakeyaml 2.x has been done on master only.

Do we need some backport?

I don't understand how you can install BlueOcean if the core requirement exceeds your current running Jenkins version.

This should be impossible when using the plugin manager.

Olivier Lamy added a comment - 2023-09-05 02:10 I wouldn't say intentional but the fix for snakeyaml 2.x has been done on master only. Do we need some backport? I don't understand how you can install BlueOcean if the core requirement exceeds your current running Jenkins version. This should be impossible when using the plugin manager.

Mark Waite added a comment - 2023-09-05 02:30 - edited

Blue ocean 1.27.5.1 is compatible with Jenkins 2.387.3 and can be installed on Jenkins 2.387.3 from the plugin manager. It doesn't include the support for snakeyaml 2.2. However, the snakeyaml 2.2 plugin is allowed to be installed on 2.387.3 because that meets its requirements for minimum Jenkins version.

Blue ocean 1.27.6 requires Jenkins 2.401.3 or newer and includes support for snakeyaml 2.2.

I'm not sure of the best way to handle the change. A backport to create 1.27.5.2 would be one way to resolve it. I suspect there are other ways to handle it as well.

Mark Waite added a comment - 2023-09-05 02:30 - edited Blue ocean 1.27.5.1 is compatible with Jenkins 2.387.3 and can be installed on Jenkins 2.387.3 from the plugin manager. It doesn't include the support for snakeyaml 2.2. However, the snakeyaml 2.2 plugin is allowed to be installed on 2.387.3 because that meets its requirements for minimum Jenkins version. Blue ocean 1.27.6 requires Jenkins 2.401.3 or newer and includes support for snakeyaml 2.2. I'm not sure of the best way to handle the change. A backport to create 1.27.5.2 would be one way to resolve it. I suspect there are other ways to handle it as well.

James Nord added a comment - 2023-09-05 08:37 - edited

> I'm not sure of the best way to handle the change

well we could bump the baseline of snakeyaml in a 2.3 so it would not be installable as an update to prevent other users on outdated jenkins versions from hitting the issue - it would however would not fix those that already installed.

Also there is no need for an API plugin to depend on latest Jenkins versions - I would always argue and API plugin should target a lower Jenkins (without dragging in detached dependencies) where it can without introducing unnecessary tech-debt.

Additionally it is a dependency of other plugins that are targetting lower versions, so that would cause issues for users installing old versions of Jenkins as the plugin dep would not e satisfiable (IIUC how the OSS UC works)?

> backport to create 1.27.5.2 would be one way to resolve

and then you need to backport other things also that are incompatible and have moved on. (k8s?)

There is no difference really here in any plugin (api or otherwise) with a breaking change and plugin dependencies. `2.387` is not supported by the community - it is 2 LTS lines out of date and has security issues.

either downgrade snakeyaml (it is not needed to be on 2.2 for any security issue) - or upgrade Jenkins and plugins.

James Nord added a comment - 2023-09-05 08:37 - edited > I'm not sure of the best way to handle the change well we could bump the baseline of snakeyaml in a 2.3 so it would not be installable as an update to prevent other users on outdated jenkins versions from hitting the issue - it would however would not fix those that already installed. Also there is no need for an API plugin to depend on latest Jenkins versions - I would always argue and API plugin should target a lower Jenkins (without dragging in detached dependencies) where it can without introducing unnecessary tech-debt. Additionally it is a dependency of other plugins that are targetting lower versions, so that would cause issues for users installing old versions of Jenkins as the plugin dep would not e satisfiable (IIUC how the OSS UC works)? > backport to create 1.27.5.2 would be one way to resolve and then you need to backport other things also that are incompatible and have moved on. (k8s?) There is no difference really here in any plugin (api or otherwise) with a breaking change and plugin dependencies. `2.387` is not supported by the community - it is 2 LTS lines out of date and has security issues. either downgrade snakeyaml (it is not needed to be on 2.2 for any security issue) - or upgrade Jenkins and plugins.

Assignee:: Emilio Escobar

Reporter:: Mark Waite

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: 2023-09-05 01:04

Updated:: 2024-07-21 14:10

Resolved:: 2023-09-05 11:18

Jenkins

Details

Description

Workarounds

History

Steps to duplicate the issue:

Attachments

Attachments

Issue Links

Activity

Collapse comment: Mark Waite added a comment - 2023-09-05 01:59

Expand comment: Mark Waite added a comment - 2023-09-05 01:59

Collapse comment: Olivier Lamy added a comment - 2023-09-05 02:10

Expand comment: Olivier Lamy added a comment - 2023-09-05 02:10

Collapse comment: Mark Waite added a comment - 2023-09-05 02:30, Edited by Mark Waite - 2023-09-05 02:31

Expand comment: Mark Waite added a comment - 2023-09-05 02:30, Edited by Mark Waite - 2023-09-05 02:31

Collapse comment: James Nord added a comment - 2023-09-05 08:37, Edited by James Nord - 2023-09-05 08:39

Expand comment: James Nord added a comment - 2023-09-05 08:37, Edited by James Nord - 2023-09-05 08:39

People

Dates