Bug 1228791

Summary: Python 2.4 incompatibility in Gofer 2.6 Thread.is_alive() on EL5 fails on goferd startup
Product: Red Hat Satellite Reporter: Jeff Ortel <jortel>
Component: katello-agentAssignee: Jeff Ortel <jortel>
Status: CLOSED CURRENTRELEASE QA Contact: Tazim Kolhar <tkolhar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bmbouter, cwelton, daviddavis, dkliban, ggainey, ipanova, mhrivnak, mmccune, pcreech, rchan, tkolhar, ttereshc
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: 2015-08-12 13:58:03 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 Jeff Ortel 2015-06-05 18:17:32 UTC
Description of problem:

Python 2.4 incompatibility using Thread.is_alive() causes trace during Plugin.is_started().  Needs to use Thread.isAlive().


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

2.6.2


How reproducible:

Always


Steps to Reproduce:
1. Start goferd on the content host
2. Observe the trace in /var/log/messages
3.

Actual results:

Loaded plugins: product-id
Traceback (most recent call last):
  File "/usr/bin/goferd", line 20, in ?
    main()
  File "/usr/lib/python2.4/site-packages/gofer/agent/main.py", line 181, in main
    start(daemon)
  File "/usr/lib/python2.4/site-packages/gofer/agent/main.py", line 113, in start
    agent.start()
  File "/usr/lib/python2.4/site-packages/gofer/agent/main.py", line 76, in start
    plugin.start()
  File "/usr/lib/python2.4/site-packages/gofer/common.py", line 218, in sfn
    return fn(*args, **kwargs)
  File "/usr/lib/python2.4/site-packages/gofer/agent/plugin.py", line 264, in start
    if self.is_started:
  File "/usr/lib/python2.4/site-packages/gofer/agent/plugin.py", line 255, in is_started
    return self.scheduler.is_alive()
AttributeError: 'Scheduler' object has no attribute 'is_alive

Expected results:

Exception not raised.


Additional info:

Comment 1 Jeff Ortel 2015-06-05 18:26:21 UTC
Fixed in gofer 2.6.2.

Comment 2 Jeff Ortel 2015-06-05 18:28:39 UTC
(In reply to Jeff Ortel from comment #0)

> Version-Release number of selected component (if applicable):
> 
> 2.6.2
> 
> 
Correction: 2.6.1.

Comment 4 Jeff Ortel 2015-06-05 18:35:01 UTC
Pulp issue tracker: https://pulp.plan.io/issues/1036

Comment 5 pulp-infra@redhat.com 2015-06-08 15:00:20 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

Comment 6 pulp-infra@redhat.com 2015-06-08 15:00:21 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 7 pulp-infra@redhat.com 2015-06-08 16:00:19 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 10 Tazim Kolhar 2015-06-12 09:07:30 UTC
VERIFIED:
 rpm -qa | grep foreman
ruby193-rubygem-foreman_discovery-2.0.0.15-1.el7sat.noarch
foreman-libvirt-1.7.2.27-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.14-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
dell-pe1955-02.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
foreman-compute-1.7.2.27-1.el7sat.noarch
foreman-gce-1.7.2.27-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.2.0-8.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch
foreman-debug-1.7.2.27-1.el7sat.noarch
foreman-vmware-1.7.2.27-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.8-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.7-1.el7sat.noarch
foreman-proxy-1.7.2.5-1.el7sat.noarch
dell-pe1955-02.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
dell-pe1955-02.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.27-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-1.7.2.27-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
foreman-postgresql-1.7.2.27-1.el7sat.noarch

steps:
1. Start goferd on the content host
2. Observe the trace in /var/log/messages

No Exception raised

Comment 11 pulp-infra@redhat.com 2015-06-17 13:30:17 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

Comment 12 pulp-infra@redhat.com 2015-07-15 12:00:17 UTC
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.

Comment 13 Bryan Kearney 2015-08-11 13:23:11 UTC
This bug is slated to be released with Satellite 6.1.

Comment 14 Bryan Kearney 2015-08-12 13:58:03 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.

Comment 15 pulp-infra@redhat.com 2015-09-11 20:30:25 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.