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:
The first time new content is synced to a child node, traces are thrown in pulp log, indicating that a resource is not found. In reality, that resource is being created on initial syncs. We shouldn't be throwing errors, just go ahead and create the resource.
Version-Release number of selected component (if applicable):
katello 1.4.6-31.el6sat
How reproducible:
Steps to Reproduce:
1. Create node and try to sync i.e.,
katello -u admin -p admin node add_environment --environment Library --org "Katello Infrastructure" --id 3
katello -u admin -p admin node sync --id 3
2. While syncing this content for the first time, tail pulp log on child node.
Actual results:
(see forthcoming attachment)
Expected results:
We should cleanly handle the obviously missing directory path or what have you, and just create it silently without yelling.
Additional info:
This is an older bug which I do not envision being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.