Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1293585

Summary: activation-key product-content command show 'Request Timeout' error
Product: Red Hat Satellite Reporter: Oleksandr Shtaier <oshtaier>
Component: HammerAssignee: Zach Huntington-Meath <zhunting>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.5CC: bbuckingham, jcallaha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:37:20 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:
Attachments:
Description Flags
Screenshot that shows that UI works properly none

Description Oleksandr Shtaier 2015-12-22 09:43:32 UTC
Description of problem:
When Red Hat product is associated with existing activation key entity - we cannot read that information back through product-content command due 'Error: Request Timeout' entry in output.

Functionality works just fine for custom products/repos

Issue seems only specific to CLI as UI represents all information properly

Doesn't seem as issue specific to only one product, but, just in case, put all details here:
Product - Red Hat Enterprise Linux Server
Reposet - Red Hat Satellite Tools 6.1 (for RHEL 7 Server) (RPMs)
Repo - Red Hat Satellite Tools 6.1 for RHEL 7 Server RPMs x86_64

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

How reproducible:
Always

Steps to Reproduce:
1. Associate RH product to Activation Key 
2. Try to read data back using 'hammer -u admin -p pass activation-key product-content --id xx'

Actual results:
Error is raised

Expected results:
Data is retrieved

Additional info:

Comment 2 Oleksandr Shtaier 2015-12-22 11:56:45 UTC
Created attachment 1108619 [details]
Screenshot that shows that UI works properly

Comment 3 Zach Huntington-Meath 2016-03-07 16:39:33 UTC
I don't think this is an issue anymore, I have replicated the conditions mentioned in the ticket both in a development and production environment. I do not get the error mentioned from Hammer CLI, instead I get back the desired information about the activation-keys product-content. If you feel like this issue has not been resolved, please let me know.

Comment 4 jcallaha 2016-03-24 20:48:17 UTC
Verified in Satellite 6.2 Beta snap 5.1

The command now works as expected.

Comment 7 Bryan Kearney 2016-07-27 11:37:20 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.

https://access.redhat.com/errata/RHBA-2016:1501