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 859623 - Promotion of RHEL content fails with RequestTimeout but UI says promotion completed
Summary: Promotion of RHEL content fails with RequestTimeout but UI says promotion com...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-22 14:34 UTC by Og Maciel
Modified: 2014-01-27 14:21 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-27 23:51:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot (52.04 KB, image/png)
2012-09-22 14:34 UTC, Og Maciel
no flags Details

Description Og Maciel 2012-09-22 14:34:53 UTC
Created attachment 615827 [details]
Screenshot

Description of problem:

I'm not sure if this is a transient (though I've seen it twice already) since the process of syncing/promoting RHEL content worked fine before with this same code base, so I'm filing this bug to make sure everything is ok. The error I see is:

  Resources::Pulp::Repository: Request Timeout (GET /pulp/api/repositories/QE-DEV-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_6_Server_RPMs_x86_64_6Server/packages/) (RestClient::RequestTimeout)

For what is worth, my system was acting pretty slow and syncing RHEL 6.2 Server x96_64 RPMs didn't get queued up right away in the web ui. I walked away from the system for several hours and when I came back the web ui displayed that the sync had completed. That's when I tried to promote the product and saw the error. Notice that the web ui says that the promotion was applied.

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


How reproducible:


Steps to Reproduce:
1. Upload a valid manifest file
2. Enable RHEL 6.2 Server x86_64 repos for CloudForms Tools and RPMs
3. Sync repositories
4. Promote product
  
Actual results:

Web ui displays both error message and states promotion was applied

Expected results:


Additional info:

Pulp log shows:

[DEBUG: 2012-09-22 09:53:33 #9081] Resource GET request: /pulp/api/repositories/QE-DEV-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_6_Server_RPMs_x86_64_6Server/errata/?
[DEBUG: 2012-09-22 09:53:40 #9081] Processing response: 200
[DEBUG: 2012-09-22 09:53:52 #9081] Task TaskStatus (6) error

Comment 4 Og Maciel 2012-09-22 15:23:21 UTC
I re-synced the product and re-promoted it with success. I wonder if there was something going on with CDN?

Comment 6 Og Maciel 2012-09-27 23:51:16 UTC
It was probably a network blip... has worked consistently now.

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


Note You need to log in before you can comment on or make changes to this bug.