Bug 856778

Summary:	Test case failure: As a Admin I would like to know that my manifest will load as scheduled, even if katello-jobs is not running when I submit the request.
Product:	Red Hat Satellite	Reporter:	Eric Sammons <esammons>
Component:	Content Management	Assignee:	Tomas Strachota <tstrachota>
Status:	CLOSED WORKSFORME	QA Contact:	Og Maciel <omaciel>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	jrist, mmccune, msuchy, omaciel, tomckay, tstrachota
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	856777	Environment:
Last Closed:	2012-09-21 08:42:42 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:	856777
Bug Blocks:

Description Eric Sammons 2012-09-12 19:08:04 UTC

+++ This bug was initially created as a clone of Bug #856777 +++

Filed from caserun (INSERT URL HERE)

Version-Release number of selected component (if applicable):
katello-common-1.1.11-1.fc16.noarch

Steps to Reproduce: 
 1. Install a RHEL >= 6.2 system @Base minimum.
 2. Install a Katello based deployment
     1. yum install -y katello-[headpin]-all
        Note: [headpin] is optional for SAM or headpin only deployment.
 3. Configure your deployment.
     1. katello-configure --deployment=[deployment]
 4. Stop the katello-jobs service
     1. service katello-jobs stop
        or
        systemctl stop katello-jobs.service

 


 1. With katello-jobs stopped, verify with:
     1. service katello-jobs status
        or
        systemctl status katello-jobs.service
 2. Navigate to your katello deployment's web ui.
 3. Login with administrative privileges.
 4. Navigate to the Content tab (By.ID, "content")
 5. Click on Import Manifest (By.ID, "new")
 6. In the Browse field, load your manifest.
 7. Click on Import to import your manifest.

To test if the job will complete when katello-jobs starts, you must complete
the next steps on the deployment host.

 1. Start katello-jobs
     1. service katello-jobs start
        or
        systemctl start katello-jobs.service



Actual results: 
Spinner remains with status of (waiting). 

'''' logs ''''
2012-09-12T14:58:46-0400: [Worker(delayed_job host:brainslug.usersys.redhat.com pid:3594)] Starting job worker
2012-09-12T14:58:47-0400: [Worker(delayed_job host:brainslug.usersys.redhat.com pid:3594)] Provider#queue_import_manifest failed with NameError: uninitialized constant Glue::Pulp - 0 failed attempts
2012-09-12T14:58:47-0400: [Worker(delayed_job host:brainslug.usersys.redhat.com pid:3594)] PERMANENTLY removing Provider#queue_import_manifest because of 1 consecutive failures.
uninitialized constant Glue::Pulp
/usr/share/katello/app/models/system.rb:23
/usr/share/katello/app/models/task_status.rb:96:in `extended_index_attrs'
/usr/share/katello/app/models/indexed_model.rb:140:in `send'
/usr/share/katello/app/models/indexed_model.rb:140:in `to_indexed_json'
/usr/lib/ruby/gems/1.8/gems/tire-0.3.13.pre/lib/tire/index.rb:296:in `convert_document_to_json'
...
2012-09-12T14:58:47-0400: [Worker(delayed_job host:brainslug.usersys.redhat.com pid:3594)] 1 jobs processed at 1.9759 j/s, 1 failed ...

Expected results:
 1. At step 7, you should see the following with a spinner.
    Spinner Import in progress (waiting)
 2. After katello-jobs is restarted, the manifest should finish loading and
    appear in the left pane of the tupane view.

Comment 2 Tomas Strachota 2012-09-21 08:42:42 UTC

I tested this with katello-1.1.12-7.el6cf.noarch on rhel 6.2 and everything went fine. The manifest got imported immediately after katello-jobs started.