Project

Profile

Help

Issue #734

closed

Asynchronous attach in the pulp agent causes unwanted race condition

Added by jortel@redhat.com about 9 years ago. Updated almost 5 years ago.

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

Description

As part of the work to delete the agent queues the pulp agent was changed to asynchronously validate registration and attach to the broker. This introduced a race condition race condition which can result in RMI requests failing because the plugin has not been completely initialized before the gofer scheduler is started.

Actions #1

Updated by jortel@redhat.com about 9 years ago

  • Status changed from NEW to POST
Actions #2

Updated by jortel@redhat.com about 9 years ago

  • Status changed from POST to MODIFIED
Actions #3

Updated by dkliban@redhat.com about 9 years ago

  • Status changed from MODIFIED to 5
Actions #4

Updated by jortel@redhat.com about 9 years ago

This can be verified by simply registering a consumer and noting the 'attached' message in the log. Just needs to be regression tested.

Actions #5

Updated by pthomas@redhat.com about 9 years ago

  • Status changed from 5 to 6

verified.

The agent registration and consumer has been regression tested.

Actions #6

Updated by bmbouter almost 9 years ago

  • Severity changed from High to 3. High
Actions #7

Updated by rbarlow almost 9 years ago

  • Status changed from 6 to CLOSED - CURRENTRELEASE
Actions #9

Updated by bmbouter almost 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF