Project

Profile

Help

Issue #297

closed

Http Event Listener: repo.sync.finish fires with task in running state

Added by mkovacik@redhat.com about 9 years ago. Updated almost 4 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.6 Beta
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

When pulp.sync.finish http event listener is triggered, the related repo sync task is still in running state

Version:
pulp-server-2.6.0-0.7.beta.fc21.noarch

How reproducible:
Always, automated

Steps to reproduce:

  1. as in the test case
    - create an rpm repo with feed
    - create http event listener
    - POSTing to http://requestb.in/bin_id
    - update the event listener to types: ['repo.sync.finish']
    - sync the repo
    - wait till repo sync tasks finish
    - check the request bin for POSTed requests

Actual Results:
- the bin contains a request, request.body with a task call report such that task.state == 'running'

Expected Results:
- the bin contains a request, request.body with a task call report such that task.state == 'finished'

Additional Information:
pulp-automation test case: test_23_event_listener.py:EventListenerTest.test_03_repo_sync_finish
https://github.com/RedHatQE/pulp-automation/blob/master/tests/general_tests/test_23_event_listener.py


Files

screen.log (34.7 KB) screen.log mkovacik@redhat.com, 02/25/2015 11:50 AM

Related issues

Related to Pulp - Issue #301: Http Event Listener: repo.sync.finish: task error not reported CLOSED - WONTFIXActions

Also available in: Atom PDF