A number of customer bug reports have been traced to the fact that the NX2->NX3 migration REST API is using encoded slashes in requests. This causes problems with reverse proxies, and so far our recommendation is to fine tune the reverse proxy settings. This will continue to be problematic in the future, so let's adjust to eliminate the encoding.
The problem manifests itself when the HTTP download option is used during upgrade to Nexus 3, and Nexus 3 is sending requests for artifacts to Nexus 2. Nexus 3 sends requests to Nexus 2 with encoded slashes like
<base url>/service/siesta/migrationagent/repository-content/npmproxy/which%2F-%2Fwhich-1.0.9.tgz, those decoded slashes need to arrive at the Nexus 2 instance unaltered/undecoded in order for migration to work.
Requests by the Nexus migration agent to Nexus 2 will fail with 404 not found. Example stack trace from your nexus.log:
This can happen with any repository type.
- Remove slash encoding from the NX2 migration REST API so that we don't have problems with reverse proxies.
- Revert note added by https://github.com/sonatype/nexus-book-internal/pull/55 which will become obsolete
- configure Nexus 3 to send requests to Nexus 2 directly instead of going through an intermediary reverse proxy
- configure the httpd in front of Nexus 2 with the directive AllowEncodedSlashes NoDecode and the option nocanon for your ProxyPass directive - do a similar change for nginx if using that server
- upgrade to 2.14.3/3.2.1 once released