Bug 1330588

Summary: Capsule page fails to show storage information under RHEL 6 system
Product: Red Hat Satellite Reporter: Og Maciel <omaciel>
Component: CapsuleAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham
Target Milestone: UnspecifiedKeywords: PrioBumpQA
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-26 18:54:17 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:
Attachments:
Description Flags
Log
none
Screenshot showing error on the UI none

Description Og Maciel 2016-04-26 14:12:48 UTC
Created attachment 1150971 [details]
Log

Description of problem:

I have 2 external capsules associated to my Satellite 6.2.0 system:

* Capsule1: installed on a RHEL 6.7 system
* Capsule2: installed on a RHEL 7.2 system

When I visit the Capsules page (Infrastructure > Capsules) and select Capsule1, under the Overview tab, the "Pulp storage" section shows "Error retrieving Pulp storage". Selecting Capsule2 I see storage information.

Logs show: ActiveRecord::RecordInvalid: Validation failed: Fact name has already been taken

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

* Satellite 6.2.0 SNAP 9.2
* satellite-capsule-6.2.0-9.0.beta.el6sat.noarch

How reproducible:


Steps to Reproduce:
1. Install, configure and associate an external capsule running on RHEL 6.7 to your Satellite 6.2.0
2.
3.

Actual results:


Expected results:


Additional info:

See log attached

Comment 1 Og Maciel 2016-04-26 14:14:28 UTC
Created attachment 1150972 [details]
Screenshot showing error on the UI

Screenshot showing error on the UI

Comment 3 Brad Buckingham 2016-04-26 18:54:17 UTC

*** This bug has been marked as a duplicate of bug 1330222 ***