Nexus3: Automated Setup fails about helm-charts

[Jasper-Ben]

nvm. overlooked the breaking changes on the properties settings 😄

[Jasper-Ben]

@stevehipwell Looking good so far! 👍 Will do some more configuring over the next couple of days. If I notice any issues I will open a new issue and/or pull request. Thanks for your awesome help so far, highly appreciated! 😃

[Jasper-Ben]

It seems the properties are not correctly added to the properties file:

bash-4.4$ cat nexus.properties 
true
[nexus.scripts.allowCreation=true]

[Jasper-Ben]

Hmm... I'm still struggling with the scripts however (log attached). Will take a closer look tomorrow.

nexus.log

[stevehipwell]

@Jasper-Ben this should be resolved in the next release. I wrote this chart for a specific use and although I've tried to make it work correctly there are cases when it's not used as we use it (including the various upgrades, which is why we've never had an etc issue due to the file system from earlier chart versions) that need resolving.

[Jasper-Ben]

@stevehipwell I am currently recreating the persistent volume on each try, so existing etc directories should not be at fault here.
It seems that not having a LDAP configured (ldap.enabled=false) does not work with the current configure.sh script, as it still tries to run the ldap.groovy script.

+ json_file=/opt/sonatype/nexus/conf/ldap.json
+ '[' -f /opt/sonatype/nexus/conf/ldap.json ']'
+ '[' -f /opt/sonatype/nexus/secret/ldap.password ']'
++ curl -s -o /dev/null -w '%{http_code}' -X POST -H 'Content-Type: application/json' -u admin:XXXXX -d @/opt/sonatype/nexus/conf/ldap.json http://localhost:8081/service/rest/v1/script/ldap/run
+ status_code=400
+ '[' 400 -ne 200 ']'
+ echo 'Could not set LDAP.'
Could not set LDAP.

with following ldap.json settings:

{"enabled":false,"password":"PASSWORD"}

[Jasper-Ben]

I just noticed your new release. Will try it now.

[Jasper-Ben]

The LDAP part seems to work now. However, now I am running into an issue with the cleanup script:

Updating script /opt/sonatype/nexus/conf/task.groovy.

2020-07-15 12:07:22,602+0000 WARN  [qtp1378315085-41] admin org.sonatype.nexus.siesta.internal.WebappExceptionMapper - (ID 93867451-692e-4d4b-ab55-0d17a6ab35b6) Response: [404] (no entity/body); mapped from: javax.ws.rs.NotFoundException: Script with name: 'task' not found

2020-07-15 12:07:22,634+0000 INFO  [qtp1378315085-43] admin org.sonatype.nexus.internal.script.groovy.GroovyScriptEngineFactory - Created engine: org.sonatype.nexus.internal.script.groovy.GroovyScriptEngine@6579bd0d

2020-07-15 12:07:23,544+0000 ERROR [qtp1378315085-43] admin org.sonatype.nexus.script.plugin.internal.rest.ScriptResource - Exception in script execution for script named: cleanup

javax.script.ScriptException: javax.script.ScriptException: com.orientechnologies.orient.core.exception.OValidationException: The field 'cleanup.mode' cannot be null, record: cleanup{name:null,notes:null,format:null,mode:null,criteria:null}

[stevehipwell]

@Jasper-Ben what does you current values.yaml file look like?

[Jasper-Ben]

@stevehipwell

image: 
  tag: "3.25.0"
  pullPolicy: "IfNotPresent"
config:
  enabled: true
  rootPassword:
    secret: "root-password"
    key: "password"
  ldap:
    enabled: false
  anonymous:
    enabled: false
  realms:
    enabled: false
#  repos:
#    - name: "docker-registry"
#      type: "docker-hosted"
#      online: true
#      attributes:
#        storage:
#          blobStorageName: "default"
#          strictContentTypeValidation: true
#          writePolicy: "ALLOW"
#      cleanup:
#        policyName: "ExampleCleanup"
#    - name: "helm-registry"
#      type: "helm-hosted"
#      online: true
#      attributes:
#        storage:
#          blobStorageName: "default"
#          strictContentTypeValidation: true
#          writePolicy: "ALLOW"
#      cleanup:
#        policyName: "ExampleCleanup"
persistence:
  enabled: true
  existingClaim: "pvc-nexus3"

[stevehipwell]

@Jasper-Ben try the latest v2.5.3 release. There was a regression in the default values that provided repos, cleanups and tasks; you've turned on the config so are getting a yaml merge of your values and the incorrect default ones.