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 1230273

Summary: check backend services prior to every action that needs it
Product: Red Hat Satellite Reporter: Justin Sherrill <jsherril>
Component: UsabilityAssignee: Justin Sherrill <jsherril>
Status: CLOSED CURRENTRELEASE QA Contact: Tazim Kolhar <tkolhar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: cwelton, dlobatog, jsherril, mmccune, tkolhar
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/10725
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 16:03:15 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:

Description Justin Sherrill 2015-06-10 14:15:10 UTC
Description of problem:



for things like content view publish/promote, repo create/enable/disable/delete possibly others

That way the action won't even start if we know a service is down.

Comment 1 Justin Sherrill 2015-06-10 14:16:32 UTC
Connecting redmine issue http://projects.theforeman.org/issues/10725 from this bug

Comment 4 Bryan Kearney 2015-06-15 14:39:51 UTC
Upstream bug assigned to jsherril

Comment 5 Bryan Kearney 2015-06-15 14:39:52 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/10725 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|313d22361610722afd50f2ed147865c0ae31cf5c.

Comment 6 Justin Sherrill 2015-06-16 17:07:10 UTC
NOTE: this will need an additional fix backported to downstream

Comment 7 Justin Sherrill 2015-06-19 18:01:41 UTC
additional fix needed:  https://github.com/Katello/katello/pull/5316

Comment 10 Bryan Kearney 2015-06-26 14:32:46 UTC
Delivered in Snap10

Comment 11 Tazim Kolhar 2015-07-15 06:44:45 UTC
Hi,

   please provide verification steps
   thanks in advance

Thanks and Regards,
Tazim

Comment 12 Justin Sherrill 2015-07-15 12:54:31 UTC
This was described in an email recently, re-pasting here:


The way it was added was such that any action that requires one or more backend services, will have just those backend services checked.  Because of this I can't give you an exhaustive list, but I can give you a short list of the major actions:

Candlepin: Pulp & ES:
Content View Publish
Content view Promote
Content View Version Remove
Repo create
Repo destroy
Repo enable

Pulp & ES:
Repo Sync

Candlepin & ES only:
Product create
Organization Create


For checking with candlepin or elasticsearch, simply shutting down tomcat/tomcat6 or elasticsearch is good enough.

For testing pulp, you can try shutting down mongod, qpidd, pulp_workers, or pulp_celerybeat

I believe this is a delay before pulp realizes that workers disappear (like 60 seconds or so), but I am unsure.  It wouldn't surprise me if you find some bugs in the pulp detection of worker health.

Comment 13 Tazim Kolhar 2015-07-16 07:26:43 UTC
VERIFIED:
# rpm -qa | grep foreman
foreman-proxy-1.7.2.5-1.el7sat.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-client-1.0-1.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-1.0-2.noarch
foreman-gce-1.7.2.30-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-debug-1.7.2.30-1.el7sat.noarch
foreman-postgresql-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.17-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
foreman-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.18-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.2.0-8.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el7sat.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-compute-1.7.2.30-1.el7sat.noarch
foreman-vmware-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-libvirt-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.8-1.el7sat.noarch
puppet-foreman_scap_client-0.3.3-9.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-ovirt-1.7.2.30-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch


steps:

stop pulp, candlepin and elasticsearch services 

# hammer product create --name tp --organization-id 1
[Foreman] Username: admin
[Foreman] Password for admin: 
Could not create the product:
  There was an issue with the backend service candlepin: Connection refused - connect(2)

# hammer content-view create --name con_t --organization-id 1
[Foreman] Username: admin
[Foreman] Password for admin: 
Could not create the content view:
  Connection refused - connect(2)

Comment 14 Bryan Kearney 2015-08-12 16:03:15 UTC
This bug was fixed in Satellite 6.1.1 which was delivered on 12 August, 2015.