Opened 14 months ago
Closed 6 months ago
#2932 closed task (fixed)
Upgrade nexus to 3.57.0 or higher
| Reported by: | robe | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Sysadmin Contract 2024-I |
| Component: | SysAdmin | Keywords: | |
| Cc: |
Description (last modified by )
repo.osgeo.org is currently on 3.45.1
Latest available nexus is 3.57.0
More than a year has passed since our upgrade
there are no CVEE fixes noted, and most changes since seem to be around PostgreSQL as backend store (which we are not using, we are using the built-in database), Ruby Gems, Conan repo. There is also a name change from Nexus Repository to Sonatype Nexus Repository.
One caution noted in the upgrades is possible issue with custom plugins.
"There is a known issue in Sonatype Nexus Repository 3.53.0 impacting those using community or custom plugins. These plugins will not load from the typical install directory and, in some cases, this may prevent Sonatype Nexus Repository from starting.
If you are using community or custom plugins and wish to upgrade, remove the plugin before doing so. Otherwise, wait to upgrade until we release a fix for this issue.
If you are not using community or custom plugins, there is no impact."
so I'll probably hold off for a bit longer till the next release comes out just in case.
Change History (4)
comment:1 by , 12 months ago
| Description: | modified (diff) |
|---|---|
| Summary: | Upgrade nexus to 3.53.1 or higher → Upgrade nexus to 3.57.0 or higher |
comment:2 by , 6 months ago
| Milestone: | Sysadmin Contract 2023-I → Sysadmin Contract 2024-I |
|---|
comment:3 by , 6 months ago
I've started the upgrade process for this and also plan to upgrade the OS from buster to bullseye.
Will be upgraded to latest nexus which is currently 3.63.0
comment:4 by , 6 months ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This is done, but I ran into some stumbling blocks with upgrading from buster to bullseye.
After I upgraded to bullseye, docker wouldn't start up. I finally ended up removing apparmor, as that seemed to be what was preventing it, and I noticed as part of the docker dist-upgrade it installed apparmor. I recall running into this issue before.
But sadly before I tried that, I made the mistake of trying to run the container priviledge with security.priveleged=true, which cause it to hang.
Long story short, I copied it to new container called nexus-2, and switched all the nginx configs to that one. Probably will require osgeo3 reboot before I can delete the old one and move back to its original name. I'll try that some other time.
Moving my prior still open items to the next proposed Milestone