Bug 834010

Summary: Manifest import fail after creating a custom product
Product: Red Hat Satellite Reporter: Chris Pelland <cpelland>
Component: WebUIAssignee: Jason E. Rist <jrist>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.1CC: cpelland, dmacpher, gkhachik, hhovsepy, inecas, jlaska, mmccune, omaciel, sghai, tomckay
Target Milestone: UnspecifiedKeywords: Triaged, ZStream
Target Release: Unused   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
A code regression caused manifest imports to fail immediately after the creation of a custom product. This update fixes the regression and provides successful manifest imports.
Story Points: ---
Clone Of: 829208 Environment:
Last Closed: 2012-07-10 07:25:45 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: 829208    
Bug Blocks:    

Comment 3 Dan Macpherson 2012-06-24 16:28:40 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
A code regression caused manifest imports to fail immediately after the creation of a custom product. This update fixes the regression and provides successful manifest imports.

Comment 4 Sachin Ghai 2012-06-25 08:44:38 UTC
verified the reported issue with following CFSE build (2012-06-22.1) :
candlepin-0.6.5-1.el6_2.noarch
katello-glue-candlepin-0.1.318-1.el6cf.noarch
katello-0.1.318-1.el6cf.noarch
pulp-1.0.4-1.el6.noarch

I can import the manifest successfully even after creating the custom repos.


I created a custom repo of pulp and then imported the manifest in org1. Later I created a new org org2 and imported another manifest in org2. Both manifests are imported successfully.

so moving this to verified.

Comment 6 errata-xmlrpc 2012-07-10 07:25:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-1062.html

Comment 7 Mike McCune 2013-08-16 18:07:31 UTC
getting rid of 6.0.0 version since that doesn't exist