Jobs were not apeearing on console after HashiCorp Vault Plugin Version upgrade to 364.vf5d54b_3dc313

[baban-babs]

Jenkins and plugins versions report

Environment

2024-01-31 06:59:42.910+0000 [id=35856] WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: h.hasPermission(it, permission) in /jenkins/job/jobname/. Reason: java.lang.NullPointerException: Cannot invoke "hudson.model.ViewGroup.getACL()" because the return value of "hudson.model.View.getOwner()" is null
java.lang.NullPointerException: Cannot invoke "hudson.model.ViewGroup.getACL()" because the return value of "hudson.model.View.getOwner()" is null

What Operating System are you using (both controller, and any agents involved in the problem)?

Red Hat Linux

Reproduction steps

1 Upgrade HashiCorp Vault Plugin to Version 364.vf5d54b_3dc313
2 Restart the Jenkins Controller
3 Once you click on job folder, you will encounter some error on console and job will be not visible

Expected Results

Job should be visible

Actual Results

Job not visible on Jenkins Controller GUI. Reporting error .

Anything else?

No response

Are you interested in contributing a fix?

No response

[brian-leveille]

I have this issue also.

[baban-babs]

I have this issue also.

Yeah i have rolled back to old plugin version. I think we need to wait for new version

[bordenit]

Same issue here. I believe it is related to this closed issue as well, as I saw that error initially and then removed the tokenExpiry to see this new error. #323 Only happening to one folder that has several nested folders in it. Last working vault plugin reference in the problematic folder is 360.v0a_1c04cf807d

[clintonsteiner]

Same issue - downleveling fixed the issue for me

[bordenit]

@clintonsteiner did you try going to latest version from 360.v0a_1c04cf807d? That's my next attempt before redoing the numerous folders. Hoping that going from 360.v0a_1c04cf807d to latest will just work.

[clintonsteiner]

@bordenit issue for me still existed with latest

[clintonsteiner]

Bumping this issue - this is a major regression introduced and we should rollback the available plugin until a fix is introduced

[clintonsteiner]

Think we should close this issue in favor of #326

[baban-babs]

Yeah this issue has been fixed now in latest vault plugin