Bug 1018896 - node sync sends confusing error the first time content is synced.
Summary: node sync sends confusing error the first time content is synced.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 16:04 UTC by Corey Welton
Modified: 2017-05-30 12:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-13 21:00:49 UTC
Target Upstream Version:


Attachments (Terms of Use)
trace in pulp log (4.23 KB, text/plain)
2013-10-14 16:05 UTC, Corey Welton
no flags Details

Description Corey Welton 2013-10-14 16:04:40 UTC
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:

Comment 1 Corey Welton 2013-10-14 16:05:45 UTC
Created attachment 812097 [details]
trace in pulp log

Comment 7 Bryan Kearney 2017-01-13 21:00:49 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.