Latest working versions?

[rvalle]

New to this module,

just trying to get it up and running.

I notice that it is not working for the latest version of nexus neither on 2.x or 3.x

I haven't looked in depth, but looks like:

in 3.x the config file has changed back to what it was in 2.x
in 2.x the package file nomemclature seems to have changed.

Has anybody noticed? or am I doing something wrong...

Beside fixing or reporting this issues. How can I know which are the latest working versions on each 2.x 3.x branch?

[kenbreeman]

Unless the config has changed in some major way this should still be working, what kind of error message are you getting? Can you post more details please?

[mvernimmen]

I'd like to chip in on part of this problem. I'm using version 1.7.0 of hubspot/nexus and it worked fine with nexus 3.0.x, but with nexus 3.1.0-04 I get this:

Error: /Stage[main]/Nexus::Config/File_line[nexus-work]: Could not evaluate: No such file or directory - /export/apps/nexus/etc/org.sonatype.nexus.cfg
Error: /Stage[main]/Nexus::Config/File_line[nexus-application-host]: Could not evaluate: No such file or directory - /export/apps/nexus/etc/org.sonatype.nexus.cfg
Error: /Stage[main]/Nexus::Config/File_line[nexus-webapp-context-path]: Could not evaluate: No such file or directory - /export/apps/nexus/etc/org.sonatype.nexus.cfg
Error: /Stage[main]/Nexus::Config/File_line[nexus-application-port]: Could not evaluate: No such file or directory - /export/apps/nexus/etc/org.sonatype.nexus.cfg
Notice: /Stage[main]/Nexus::Service/File[/lib/systemd/system/nexus.service]: Dependency File_line[nexus-application-host] has failures: true
Notice: /Stage[main]/Nexus::Service/File[/lib/systemd/system/nexus.service]: Dependency File_line[nexus-application-port] has failures: true
Notice: /Stage[main]/Nexus::Service/File[/lib/systemd/system/nexus.service]: Dependency File_line[nexus-webapp-context-path] has failures: true
Notice: /Stage[main]/Nexus::Service/File[/lib/systemd/system/nexus.service]: Dependency File_line[nexus-work] has failures: true
Warning: /Stage[main]/Nexus::Service/File[/lib/systemd/system/nexus.service]: Skipping because of failed dependencies
Notice: /Stage[main]/Nexus::Service/Service[nexus]: Dependency File_line[nexus-application-host] has failures: true
Notice: /Stage[main]/Nexus::Service/Service[nexus]: Dependency File_line[nexus-application-port] has failures: true
Notice: /Stage[main]/Nexus::Service/Service[nexus]: Dependency File_line[nexus-webapp-context-path] has failures: true
Notice: /Stage[main]/Nexus::Service/Service[nexus]: Dependency File_line[nexus-work] has failures: true
Warning: /Stage[main]/Nexus::Service/Service[nexus]: Skipping because of failed dependencies
Notice: /Stage[main]/Nexus/Anchor[nexus::done]: Dependency File_line[nexus-application-host] has failures: true
Notice: /Stage[main]/Nexus/Anchor[nexus::done]: Dependency File_line[nexus-application-port] has failures: true
Notice: /Stage[main]/Nexus/Anchor[nexus::done]: Dependency File_line[nexus-webapp-context-path] has failures: true
Notice: /Stage[main]/Nexus/Anchor[nexus::done]: Dependency File_line[nexus-work] has failures: true
Warning: /Stage[main]/Nexus/Anchor[nexus::done]: Skipping because of failed dependencies

I think that's because of the configuration change that @rvalle was talking about.

[kenbreeman]

Can you double check that the URL for the nexus package download you're using is valid? I wasn't able to reproduce this

[rvalle]

@kenbreeman with the latest 2.x the nexus_type can be set to "bundle", then the URL produced is valid, and everything seems to work fine.

@mvernimmen thats the 3.x config file change. they seem to have gone back to naming as in 2.x branch. you can quickly test by creating a symlink from org.sonatype.nexus.cfg to nexus.properties, then the puppet will run.

[mvernimmen]

@rvalle thanks, indeed that symlink fixes it.

[gbloquel]

After reading the last upgrade from Nexus 3.0.2 to 3.1. See Upgrade Nexus 3.0.2 to 3.1.0

For the compatibilty with nexus 3.1 there are many changes to do in the puppet module.

• the data folder is not at the same location
• the config file is nexus.properties instead of org.sonatype.nexus.cfg

[DarthHater]

@gbloquel is correct, we've made quite a few configuration changes between 3.0 and 3.1, I would imagine these would cause it to not work now.

[WetHippie]

Having similar problems having upgraded from 3.0 to current latest (3.2.1 as of today)

Notice: /Stage[main]/Nexus::Package/File[/opt/nexus]/target: target changed '/opt/nexus-3.0.0-03' to '/opt/nexus-3.2.1-01' Info: Class[Nexus::Package]: Scheduling refresh of Class[Nexus::Service] Error: /Stage[main]/Nexus::Config/File_line[nexus-application-host]: Could not evaluate: No such file or directory @ rb_sysopen - /opt/nexus/etc/org.sonatype.nexus.cfg Error: /Stage[main]/Nexus::Config/File_line[nexus-application-port]: Could not evaluate: No such file or directory @ rb_sysopen - /opt/nexus/etc/org.sonatype.nexus.cfg Error: /Stage[main]/Nexus::Config/File_line[nexus-webapp-context-path]: Could not evaluate: No such file or directory @ rb_sysopen - /opt/nexus/etc/org.sonatype.nexus.cfg Error: /Stage[main]/Nexus::Config/File_line[nexus-work]: Could not evaluate: No such file or directory @ rb_sysopen - /opt/nexus/etc/org.sonatype.nexus.cfg