daviddavis@redhat.com
daviddavis@redhat.com- Registered on: 02/19/2015
- Last connection: 09/25/2017
Issues
- Assigned issues: 13
- Reported issues: 58
Projects
- Pulp (Developer, Private Access, 02/19/2015)
- RPM Support (Developer, Private Access, 02/19/2015)
- Puppet Support (Developer, Private Access, 02/19/2015)
- Docker Support (Developer, Private Access, 02/19/2015)
- Python Support (Developer, Private Access, 02/19/2015)
- Packaging (Developer, Private Access, 02/19/2015)
- Crane (Developer, Private Access, 02/19/2015)
- Puppet Deployment [deprecated] (Developer, Private Access, 02/19/2015)
- OSTree Support (Developer, Private Access, 02/19/2015)
- Debian Support (Developer, Private Access, 02/19/2015)
- Nectar (Developer, Private Access, 02/19/2015)
- OpenStack Support (Developer, Private Access, 02/19/2015)
- External (Developer, Private Access, 03/21/2017)
- File Support (Developer, Private Access, 07/17/2017)
- Example (Developer, Private Access, 09/22/2017)
Activity
09/22/2017
-
If we require 2.3.2, we should:
- Update the docs (README?) to say that ansible 2.3.2+ is required
- Require ansible 2.3.2+ in the ansible version assertion Issue #3026: Getting an error with venv during vagrant up of pulp 3.0 dev environmentIf you vagrant up on ansible 2.3.1 (the current version in epel7), you get an error:...
09/21/2017
-
A couple things: it looks like F25 is on 2.3.2 which fixes the problem. Also, rhel-7-server-extras-rpms offers 2.3.2. So really, this just affects CentOS 7 (the OS I am on) which still has 2.3.1 (via epel7).
I've been able to work ar... Issue #3026: Getting an error with venv during vagrant up of pulp 3.0 dev environmentIf you vagrant up on ansible 2.3.1 (the current version in epel7), you get an error:... -
If you vagrant up on ansible 2.3.1 (the current version in epel7), you get an error:...· Created issue
09/20/2017
-
The django documentation recommends adding migrations to source control [0] so I think we ought to do option 3. Maybe not for the alpha but eventually.
Would recreating migrations on each model change be possible with upgrades? If a u... Issue #3012: db-reset script fails to migrate...
09/19/2017
-
Asked for updates but have not heard anything. Issue #2995: Workers work exclusively on a single qpid queue before moving onto the next queueUsing Celery 3, I have the following code in a blah.py file:...
09/15/2017
-
Doing some more research, it looks like celery closes db connections on worker init when using django:
https://github.com/celery/celery/blob/master/celery/fixups/django.py#L135-L155
I think we can apply this same logic to mongo and... Issue #2979: Celery workers may deadlock when PULP_MAX_TASKS_PER_CHILD and mongo replica set are ...If the PULP_MAX_TASKS_PER_CHILD option in /etc/default/pulp_workers is uncommented, and a mongodb replica set is used, celery workers are prone to deadlock when handling tasks. When this happens, all tasks assigned to the deadlocked wor... -
-
09/12/2017
-
Issue #2979 (ASSIGNED): Celery workers may deadlock when PULP_MAX_TASKS_PER_CHILD and mongo repli...If the PULP_MAX_TASKS_PER_CHILD option in /etc/default/pulp_workers is uncommented, and a mongodb replica set is used, celery workers are prone to deadlock when handling tasks. When this happens, all tasks assigned to the deadlocked wor...
-
Also available in: Atom
.