Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When creating a new product and adding a new yum repo but not adding any content to it sync to capsule fails with
Error: RPM1004: Error retrieving metadata: NOT FOUND
Version-Release number of selected component (if applicable):
[root@inf3 ~]# rpm -qa satellite
satellite-6.2.12-5.0.el7sat.noarch
[root@inf3 ~]# rpm -qa foreman
foreman-1.11.0.85-1.el7sat.noarch
[root@inf3 ~]#
[root@inf3 ~]# rpm -qa pulp*
pulp-katello-1.0.2-1.el7sat.noarch
pulp-docker-plugins-2.0.3.1-1.el7sat.noarch
pulp-puppet-tools-2.8.7.1-1.el7sat.noarch
pulp-puppet-plugins-2.8.7.1-1.el7sat.noarch
pulp-client-1.0-1.noarch
pulp-rpm-plugins-2.8.7.16-1.el7sat.noarch
pulp-selinux-2.8.7.15-1.el7sat.noarch
pulp-server-2.8.7.15-1.el7sat.noarch
[root@inf3 ~]#
-- should be latest 6.2.12
How reproducible:
Steps to Reproduce:
1. create a new product, add new yum repository but don't add content
2. publish content view and promote content view to LCE
3. add new LCE to capsule
4. sync capsule via hammer
Actual results:
# hammer capsule content synchronize --id 6 --organization-id 12
[.........................................................................................................................................................................................................] [100%]
Error: RPM1004: Error retrieving metadata: NOT FOUND
Expected results:
sync shall complete without error even if repository is empty
Additional info:
Played around with fore metadata creation during publish and promote:
- when forcing metadata creation during publish only --> not sufficent, capsule sync fails
- when forcing metadata creation during promote only --> repo can be synced --> capsule sync works