Bug 874426

Summary: Link to manifests missing in import history after uploading manifest
Product: [Retired] Subscription Asset Manager Reporter: Tazim Kolhar <tkolhar>
Component: katelloAssignee: Tom McKay <tomckay>
Status: CLOSED NOTABUG QA Contact: SAM QE List <sam-qe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.2CC: cwelton, tomckay
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-08 13:19:27 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:    
Bug Blocks: 816564    
Attachments:
Description Flags
manifest link
none
the manifest zip file which was used for uploading none

Description Tazim Kolhar 2012-11-08 07:49:51 UTC
Created attachment 640612 [details]
manifest link

Description of problem:

After uploading a manifests the import history containing link
to distributor from where the manifest is downloaded is missing .

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

# rpm -qa | grep katello
katello-certs-tools-1.2.1-1h.el6_3.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-common-1.2.2-1h.el6_3.noarch
katello-glue-candlepin-1.2.2-1h.el6_3.noarch
katello-cli-1.2.2-1h.el6_3.noarch
katello-selinux-1.2.1-1h.el6_3.noarch
katello-headpin-all-1.2.2-1h.el6_3.noarch
katello-headpin-1.2.2-1h.el6_3.noarch
katello-configure-1.2.1-1h.el6_3.noarch
katello-common-1.2.2-1h.el6_3.noarch

How reproducible:
# yum install -y katello-headpin-all
# katello-configure --deployment=sam

Steps to Reproduce:
1.Login to UI
2.Navigate to Content -> Redhat Subscriptions
3.Upload a manifest
4.Check import history contains link to the distributor from where
  the manifest was downloaded  
Actual results:

Link is missing

Expected results:

A link is provided 

Additional info:

Comment 1 Tazim Kolhar 2012-11-08 07:51:02 UTC
Created attachment 640619 [details]
the manifest zip file  which was used for uploading

Comment 2 Tom McKay 2012-11-08 13:19:27 UTC
Not all manifests have the required information to link back to their source. If this manifest came from the production or stage customer portal in the past week, then we can open a BZ against that system If it is older than that or from another source, then this is working as intended.

Please download try with a new manifest downloaded from production or stage and let me know.

Comment 3 Tazim Kolhar 2012-11-09 04:49:20 UTC
It works with the newly downloaded manifests.