Project

Profile

Help

Actions
Send by e-mail Copy link

Story #22

closed

As a user, I don't have to manually set the concurrency of my special workers to 1

Added by Anonymous almost 10 years ago. Updated over 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Right now, the workers must be started with the -c 1 flag. It may be possible to detect the concurrency setting of a worker as part of the babysit() process, and it also may be possible to set it to 1. If these things are possible, it would be nice if the babysit() function did that for the user, if at least just to ensure that things are working properly.

Actions
Copy link
 #1

Updated by rbarlow almost 10 years ago

  • Project changed from 22 to Pulp

Added by jortel@redhat.com over 9 years ago

Revision 0e456d3b | View on GitHub

Merge pull request #22 from jortel/entitlement

refs #99 - support repo auth.

Actions
Copy link
 #2

Updated by bmbouter over 5 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions
Copy link
 #3

Updated by bmbouter over 5 years ago

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

Actions
Copy link
 #4

Updated by bmbouter over 5 years ago

  • Tags Pulp 2 added
Actions
Send by e-mail Copy link

Also available in: Atom PDF