Open gr0l opened 9 months ago
Hi, this is a known issue to me, but only when using Postgres as a database. Do you use Postgres as well, or the default OrientDB?
I've been rewriting the cleanup policy feature to be compatible with Postgres and OrientDB. I expect to wrap this up somewhere next week.
Yes, we are using Postgres as database. Thx for your help.
@gr0l there you go :-) #416 I have tested this using an OrientDB and Postgres installation.
Please let me know if this will work for you as well. You only need the changes in the groovy script. The other file is only used for testing with molecule.
This started to happen to me too, although I'm not using Postgres.
Ansible version: 3.71.0
Role: 2.5.2
Java version:
openjdk version "17.0.11" 2024-04-16
OpenJDK Runtime Environment Temurin-17.0.11+9 (build 17.0.11+9)
OpenJDK 64-Bit Server VM Temurin-17.0.11+9 (build 17.0.11+9, mixed mode, sharing)
Have you tried it with my fork of this ansible role?
You can find it at https://github.com/CloudKrafter/nexus3-pro
It has most nexus pro features including database migrator included and most open PRs from this repo are merged back as well.
I am keeping my fork in sync with this thoteam role, on top of that I'm adding bug fixes and new features for Nexus Pro users.
Not yet, but I tried https://github.com/ansible-ThoTeam/nexus3-oss/pull/416 and it worked. Thank you!
Are you using the H2 database? Orientdb is not supported anymore, nor is Java 8 and 11.
Coukd be that the H2 database also need the same classes as the postgres implementation.
Glad my PR helps :-)
When trying to rollout cleanup policies. I got the following error:
Versions: Nexus: 3.65 Role: v2.5.2
Configuraion:
Ansible Role Log:
Nexus Log:
I also tried smaller configurations with the first entry only. It seems that the script is not able to access the class
org.sonatype.nexus.repository.search.DefaultComponentMetadataProducer
at all.