Right now this bug is proving to be a blocker for us.
Once the queue fills up then no new tasks can be executed and even if the
processes are manually killed or even if the system is rebooted they are
still in the DB.
Sometimes, an single repo sync in pulp is enough to fill up the queue.
What is the impact like for others out there?
Does anybody have a workaround?
For us we've found that we can't use Foreman as long as this bug is
I was hoping this would be fixed in Sprint 44 but it just got bumped to
Sprint 45 (this bug has been in since Sprint 42…)
The issue is being actively worked on, and has been bumped around simply
due to not arriving at a solution by the end of the given sprints. Devs are
having to look into the qpid library itself as well as build new packages
that are proving troublesome to test if upgrading them will fix the issue.
We are also going to look into disabling that particular task from running
as an option for a 2.1.Z release.
On Tue, Mar 17, 2015 at 2:37 PM, Tony Coffman wrote:
I’m in the same boat for the past couple of weeks looking for a
workaround. 2.1.1 is nearly unusable with this bug and the max open files
bug but at least I know how to work around the max files bug.
> On 2015/03/18, at 5:49, Tony Coffman wrote:
> Thanks for the update!
> You received this message because you are subscribed to a topic in the Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/foreman-users/M50pgHaZ_nQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to firstname.lastname@example.org.
> To post to this group, send email to email@example.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.