Description of problem: Uploaded RPM's, successfully published repository, but not shown in yum. Version-Release number of selected component (if applicable): pulp-server-2.5.0-1.el6.noarch How reproducible: 90% of the time. Steps to Reproduce: 1. Create new RPM 2. Upload RPM to repo using pulp-admin commands 3. Publish the repo using pulp-admin commands 4. Run a `yum clean all` and a `yum list` on a client hooked up to the repo. Actual results: The package is not listed in the repo. Expected results: The new package is listed and is available for install. Additional info: The repomd.xml file gets updated after each upload and publish and the clients yum cache is updated each time, but the package is not shown around 90% of the time. The scripts to automate this process was working fine for months on Version 2.4, it was when we upgraded to 2.5 when we hit intermittent issues, nothing else has changes. Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Description: Packages to be added: Comps group: Default: Mandatory: Visible: Multi-lib: Need to be present for arches: Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Can you upload a copy of the repomd.xml and indicate if the RPM of interest is included? Also is there anything interesting in the Pulp server log? Does the RPM upload complete without error? The Pulp server logs should show that.
Created attachment 965863 [details] Log from jenkins for the rpm upload and repo publish Attached is the log from the jenkins job which runs pulp-admin commands to upload and publish.
Created attachment 965864 [details] repomd.xml Attached is the repomd.xml created after a successful rpm upload and publish, which was presented to yum clients who could not see the new package. The pulp-admin commands however showed this package as contained within the repo.
Created attachment 965866 [details] directory listing for repodata Attached the dir listing for the repo in question. There are multiple .gz's in the directory and only one of each type (primary, updateinfo...) is referenced in the repomd.xml file.
Created attachment 965901 [details] another repomd.xml repomd.xml and referenced primary.xml
It appears that the incremental republish in this case is not making it to the end of the file and is some of the previous entries.
https://github.com/pulp/pulp/pull/1407 This fixes the item that caused the problem. It does not fix the issue for a repository that is already in an inconsistent state. The fix for that would be to remove an rpm from the repository and then add it back. That will trigger a clean republish which will fix the problem going forward.
The alternative to adding & removing the rpm from the repository is that as part of the upgrade to 2.5.1 the /var/lib/pulp/published/yum/ should be removed manually and all the repositories should be republished.
verified [root@mgmt4 ~]# rpm -qa pulp-server pulp-server-2.5.1-0.2.beta.el6.noarch [root@mgmt4 ~] 2 cases tested 1. uploaded 1 rpm to the repo & published. checked to see the rpm is available to use 2. uploaded 2 second repo & republish and check for the rpm 3. Continue to upload and republish to make sure that everything publishes correctly and the rpms are available for use. Also tested a 2nd case with upgrade instructions from comment 7 & 8
Fixed in 2.5.1-1.