Affects Version/s: 3.37.3, 3.38.1
Fix Version/s: None
Sprint:NXRM Immortals Sprint 33, NXRM Immortals Sprint 34, NXRM Immortals Sprint 35, NXRM Immortals Sprint 36, NXRM Sentinels Sprint 52
Customer reported yum-proxy remote to yum-hosted repo is not picking up yum metadata update (repomd.xml) after yum metadata is rebuilt on yum-hosted after uploading new component.
Based on analysis, it appeared the Last-Modified date is preserved and never get updated after DB migrate from Orient to H2.
Steps on 3.37.3-02
- Create yum-hosted repo and upload few assets and ensure metadata are automated generated
- Migrate orient to H2 with nexus-db-migrator-3.37.0-01.jar
- Start nexus and upload asset to yum-hosted repo
- After metadata rebuild is done (2022-05-02 09:25:24,941-0600), download the repomd.xml from yum-hosted repo with curl
Last-Modified date should be match with the metadata rebuild date (2022-05-02 09:25:24,941-0600)
Last-Modified: Fri, 29 Apr 2022 21:11:33 GMT
Also notice the content of file is updated correctly, but last_modified (2022-04-29T15:11:33.008-06:00) for repomd.xml from UI is not updated as well