Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 916551

Summary: manifest will load as scheduled, even if katello-jobs is not running when user submit the request fails if tried with cli commands
Product: [Retired] Subscription Asset Manager Reporter: Tazim Kolhar <tkolhar>
Component: katelloAssignee: Tom McKay <tomckay>
Status: CLOSED ERRATA QA Contact: Tazim Kolhar <tkolhar>
Severity: medium Docs Contact:
Priority: high    
Version: 1.3CC: cwelton, gkhachik, omaciel, tomckay
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 11:07: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:
Embargoed:
Bug Depends On:    
Bug Blocks: 833466    

Description Tazim Kolhar 2013-02-28 10:09:48 UTC
Description of problem:

manifest will load as scheduled, even if katello-jobs is not running when user submit the request fails when tried with cli commands.
Same scenario works fine if tried in UI.

The import manifests keeps loading unless the katello-jobs is restarted 


Version-Release number of selected component (if applicable):
# rpm -qa  |grep katello
katello-cli-common-1.2.1-12h.el6_3.noarch
katello-headpin-1.2.1-15h.el6_3.noarch
katello-cli-1.2.1-12h.el6_3.noarch
katello-configure-1.2.3-3h.el6_3.noarch
katello-common-1.2.1-15h.el6_3.noarch
katello-headpin-all-1.2.1-15h.el6_3.noarch
katello-certs-tools-1.2.1-1h.el6_3.noarch
katello-selinux-1.2.1-2h.el6_3.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-glue-candlepin-1.2.1-15h.el6_3.noarch
katello-repos-1.3.2-1.el6.noarch


How reproducible:

#yum install -y katello-headpin-all
#katello-configure --deployment=sam

Steps to Reproduce:

1.# service katello-jobs stop

2.# service katello-jobs status
  delayed_job is not running.
  delayed_job_monitor is not running.

  
3.# headpin -u admin -p admin provider import_manifest --name "Red Hat" --org  ACME_Corporation --file '/tmp/stack-manifest.zip'
  Manifest imported

4.# echo $?
  0

5.# service katello-jobs status
  delayed_job is not running.
  delayed_job_monitor is not running.

6.Log in to UI .
  Navigate to Contents -> Subscriptions -> Red Hat Subscriptions
  List of subscriptions visible.



Actual results:

Manifests import succeded .

Expected results:
The manifest import should be successful only after katello-jobs is restarted.
 

Additional info:

Comment 1 Tom McKay 2013-07-23 13:11:28 UTC
The CLI now uses an async job to import the manifest; it will not complete without katello-jobs running.

Comment 2 Bryan Kearney 2013-08-02 18:52:46 UTC
SNAP0 contains these bug fixes. Moving to ON_QA.

Comment 3 Tazim Kolhar 2013-08-08 12:14:09 UTC
VERIFIED :
# rpm -qa | grep katello
katello-selinux-1.4.4-2.el6sat.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-certs-tools-1.4.2-2.el6sat.noarch
katello-cli-common-1.4.3-5.el6sat.noarch
katello-cli-1.4.3-5.el6sat.noarch
katello-common-1.4.3-6.el6sam_splice.noarch
katello-configure-1.4.4-2.el6sat.noarch
katello-glue-elasticsearch-1.4.3-6.el6sam_splice.noarch
katello-headpin-all-1.4.3-6.el6sam_splice.noarch
katello-glue-candlepin-1.4.3-6.el6sam_splice.noarch
signo-katello-0.0.10-2.el6sat.noarch
katello-headpin-1.4.3-6.el6sam_splice.noarch



# service katello-jobs stop

# service katello-jobs status
delayed_job is not running.
delayed_job_monitor is not running.


# headpin -u admin -p admin provider import_manifest --org test --name 'Red Hat' --file '/root/manifest_refresh.zip'
Provider [ Red Hat ] manifest import complete

# service katello-jobs restart
Stopping katello-jobs: [FAILED]
Starting katello-jobs: [  OK  ]


The manifests uploading keeps loading until the service is started using other
terminal

Comment 5 errata-xmlrpc 2013-10-01 11:07:17 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.

http://rhn.redhat.com/errata/RHEA-2013-1390.html