Bug 1193663

Summary: raised unexpected: IOError('NOT FOUND',) when synchronizing non-existing docker image
Product: Red Hat Satellite Reporter: Og Maciel <omaciel>
Component: Container Management - ContentAssignee: Tom McKay <tomckay>
Status: CLOSED DEFERRED QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: bkearney, cwelton, daviddavis, mmccune, tomckay
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-13 20:12:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1193674    
Bug Blocks: 1190289    
Attachments:
Description Flags
screenshot
none
log none

Description Og Maciel 2015-02-17 20:39:38 UTC 
Created attachment 992878 [details]
screenshot

Description of problem:

Synchronizing a Docker-based repository for a non-existing image generates a scary looking stacktrace in the backend but the UI shows that something failed (screenshot attached). I feel that the stacktrace could be handled a bit better and that maybe we should handle this a bit differently and in a way that it is more useful to the end user?


Version-Release number of selected component (if applicable):

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.42-1.el6.noarch
* candlepin-common-1.0.21-1.el6.noarch
* candlepin-selinux-0.9.42-1.el6.noarch
* candlepin-tomcat6-0.9.42-1.el6.noarch
* elasticsearch-0.90.10-7.el6.noarch
* foreman-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* foreman-compute-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* foreman-debug-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* foreman-gce-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* foreman-libvirt-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* foreman-ovirt-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* foreman-postgresql-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* foreman-proxy-1.8.0-0.develop.201502121459git0207401.el6.noarch
* foreman-release-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* foreman-selinux-1.8.0-0.develop.201412151103gite2863e4.el6.noarch
* foreman-vmware-1.8.0-0.develop.201502121510git9edf91b.el6.noarch
* katello-2.2.0-1.201502171650git5cf9de7.el6.noarch
* katello-certs-tools-2.0.1-1.el6.noarch
* katello-common-2.2.0-1.201502171650git5cf9de7.el6.noarch
* katello-default-ca-1.0-1.noarch
* katello-installer-2.2.0-1.201502160627gite8ff373.el6.noarch
* katello-installer-base-2.2.0-1.201502160627gite8ff373.el6.noarch
* katello-repos-2.1.1-1.el6.noarch
* katello-server-ca-1.0-1.noarch
* openldap-2.4.39-8.el6.x86_64
* pulp-docker-plugins-0.2.2-1.el6.noarch
* pulp-katello-0.3-3.el6.noarch
* pulp-nodes-common-2.6.0-0.7.beta.el6.noarch
* pulp-nodes-parent-2.6.0-0.7.beta.el6.noarch
* pulp-puppet-plugins-2.6.0-0.7.beta.el6.noarch
* pulp-puppet-tools-2.6.0-0.7.beta.el6.noarch
* pulp-rpm-plugins-2.6.0-0.7.beta.el6.noarch
* pulp-selinux-2.6.0-0.7.beta.el6.noarch
* pulp-server-2.6.0-0.7.beta.el6.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.3.3-1.el6.noarch
* ruby193-rubygem-net-ldap-0.10.0-1.el6.noarch
* ruby193-rubygem-runcible-1.3.1-1.el6.noarch
* rubygem-hammer_cli-0.1.4-1.201502121207git0ab2866.el6.noarch
* rubygem-hammer_cli_foreman-0.1.4-1.201501221305git706b057.el6.noarch
* rubygem-hammer_cli_foreman_bootdisk-0.1.2-1.el6.noarch
* rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410gitc96619d.git.0.37f3704.el6.noarch
* rubygem-hammer_cli_gutterball-0.0.1-1.201501072024git01fe139.git.0.06e884f.el6.noarch
* rubygem-hammer_cli_import-0.10.4-1.el6.noarch
* rubygem-hammer_cli_katello-0.0.7-1.201502061831git68a34d6.git.0.9c4412d.el6.noarch
* sssd-ldap-1.11.6-30.el6.x86_64


How reproducible:


Steps to Reproduce:
1. Create a custom product
2. Create a custom docker-based repository for mongodb (the upstream name should be mongodb and you should point to https://registry.hub.docker.com)
3. Sync it

Actual results:

Stacktrace shows up in /var/log/messages

Expected results:


Additional info:
Comment 1 Og Maciel 2015-02-17 20:40:30 UTC 
Created attachment 992879 [details]
log
Comment 2 David Davis 2015-02-17 21:08:05 UTC 
I think the Rails stacktraces are ok since we are receiving an error from pulp. Also, they're pretty easy to understand (I think but let me know if you disagree). I'll open a pulp bug though regarding their stacktraces.
Comment 4 Bryan Kearney 2017-03-13 20:12:24 UTC 
I do not see this bug being addressed in the near term. If you believe closing this is an issue, please feel free to re-open with additional information.