nexus 2.3 doesn't recognize new rpm

[Riccardo Setti]

Hi,

after updating to nexus 2.3, and, therefore dropped the needs of the yum plugin new deployed rpm 

are not included anymore in the repo.

I can see them via the UI but createrepo is not able to find them. 

Do you have a clue? Do you need more informations?

Thanks,

R

[Herold, Sebastian]

Could you please provide the corresponding part of the nexus.log?

Thanks,
Sebastian

[Riccardo Setti]

jvm 1    | 505/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.1-1/gilt-svc-persistent-session-0.0.1-1.rpm   

jvm 1    | 506/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.10-1/gilt-svc-persistent-session-0.0.10-1.rpm     

jvm 1    | 507/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.2-1/gilt-svc-persistent-session-0.0.2-1.rpm 

jvm 1    | 508/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.3-1/gilt-svc-persistent-session-0.0.3-1.rpm                                                                                           

jvm 1    | 509/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.4-1/gilt-svc-persistent-session-0.0.4-1.rpm                                                                                                

jvm 1    | 510/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.5-1/gilt-svc-persistent-session-0.0.5-1.rpm 

jvm 1    | 511/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.6-1/gilt-svc-persistent-session-0.0.6-1.rpm                                                                                                   

jvm 1    | 512/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.7-1/gilt-svc-persistent-session-0.0.7-1.rpm                                  

jvm 1    | 513/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.8-1/gilt-svc-persistent-session-0.0.8-1.rpm

jvm 1    | 514/564 * com/giltgroupe/gilt-svc-persistent-session/0.0.9-1/gilt-svc-persistent-session-0.0.9-1.rpm    

but version 0.0.12 and 0.0.13 are not discovered, i can see them through the UI

how can I add more debug?

[Riccardo Setti]

more info:

I deleted repodata for that particular repo and run the yum-metadata task again against the repo

in order to be sure that i was downloading the new indexes i run

yum clean all 

on the client

rpm deployed before the upgrade are visible / found.

[Riccardo Setti]

running createrepo by hand worked fine

[Herold, Sebastian]

The documentation isn't outdated, sorry. In Nexus 2.3 you need to configure "Yum: Generate Metadata" capabilities for each RPM repository under "Administration" -> "Capabilities". After uploading the next RPM, it should work.

[Herold, Sebastian]

Sorry, again -> The documentation IS outdated.

[Riccardo Setti]

Hey,

there is a particular way to deploy an rpm, because we usually go with:

mvn deploy:file target and it seems even after adding the capability metadata are not re-generated

[Herold, Sebastian]

mvn deploy:file to a capable repository should be fine. Could you please send me the corresponding snippet of the nexus.log?

Regards,

Sebastian

--
Sie haben diese Nachricht erhalten, weil Sie der Google Groups-Gruppe Nexus Yum Plugin beigetreten sind.
Um Ihr Abonnement für diese Gruppe zu beenden und keine E-Mails mehr von dieser Gruppe zu erhalten, senden Sie eine Email an nexus-yum-plug...@googlegroups.com.
Weitere Optionen: https://groups.google.com/groups/opt_out
 
 

[Riccardo Setti]

Sorry I made some mistake while adding the capability for our production repo. It seems to work perfectly right now! Thanks!

How can we update the documentation?

[Herold, Sebastian]

You can update the documentation by sending a pull request via GitHub. Thanks in advance.