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 1334627

Summary: Error uploading Manifest
Product: Red Hat Satellite Reporter: jnikolak
Component: CandlepinAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DEFERRED QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: egolov, mmccune
Target Milestone: Unspecified   
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-05-11 05:54:56 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: 1313551    
Bug Blocks:    
Attachments:
Description Flags
manifest_sub_error
none
foreman_debug3 none

Description jnikolak 2016-05-10 08:08:52 UTC 
Created attachment 1155611 [details]
manifest_sub_error

Description of problem:

Manifest fails to upload


Steps to Reproduce:
1. generate a new manifest on customer portal
2. Ensure that pulp is not running(this was not intentional to find the bug)
3. Try to upload the manifest just generated
4. It will fail with error:
Katello::Resources::Candlepin::Owner: Request Timeout  (POST /candlepin/owners/MyOrg/imports)

5. Then start katello to ensure all services are up
# hammer ping to confirm

6. Try to upload the manifest but it gives error message
Import is the same as existing data

However on the left frame, it shows no subscriptions.

Attached screenshot.


Issue resolved by doing:
https://access.redhat.com/solutions/2305331
Comment 1 jnikolak 2016-05-10 08:16:42 UTC 
Created attachment 1155613 [details]
foreman_debug3
Comment 2 Evgeni Golov 2016-05-10 08:20:45 UTC 
I also encountered that on my testinstall, however my pulp was running fine while the initial import of the Manifest errored out with "RestClient::RequestTimeout: Katello::Resources::Candlepin::Owner: Request Timeout  (POST /candlepin/owners/ACME/imports)"

For me just clicking "refresh manifest" was enough to fix that issue, though.
Comment 3 Barnaby Court 2016-05-10 13:22:30 UTC 
This will require changing the manifest import from a synchronous to an asynchronous call. See the upstream bug for the details of that call.
Comment 4 Mike McCune 2016-05-11 05:54:56 UTC 
If Pulp isn't running, many many things will fail besides manifest import. We currently require all services to be running for Satellite to be functional and anything less is an error state that must be resolved before continuing.

This isn't new for 6.2, and would behave the same in 6.1 or older.

That said, Satellite should show the user in a much more obvious manner that required services are not functioning upon login. If Pulp was down, we should have a big banner/error or something that indicates they should cease trying to utilize the Satellite and resolve the issue. 

Essentially a heartbeat or monitor to notify that things weren't working properly.  I searched for an RFE in this area and couldn't find one so I filed a new one:

https://bugzilla.redhat.com/show_bug.cgi?id=1334992


feel free to comment there.

As for Evgeni's comment here:

https://bugzilla.redhat.com/show_bug.cgi?id=1334627#c2

that is a valid issue worth investigating but is a different bug that I filed here:

https://bugzilla.redhat.com/show_bug.cgi?id=1334996

this is a genuine issue, our default timeout needs to be increased, I'm glad this was spotted as it often only occurs with large manifests or slower VMs.

I'm going to close the original bug because it is a bit vague and I'd prefer to have 2 different bugs to handle this.

Mike