A timing window exists where it is possible that Auto-Errata Updates are not scheduled for servers they are applicable to. The Taskomatic ErrataQueue job is the thing that schedules the update actions for servers that have Auto Errata Updates turned on. However, it depends on the data updated by the ErrataCache job to know which servers the errata are applicable to. Consequently, ErrataQueue will not start processing a channel if ErrataCache is still running on that channel. However, the ErrataCache worker removes the job from the queue for the channel it's working on before it is finished. This creates a timing window that potentially allows ErrataQueue to process the channel before EC is done and decide (based on the incomplete ErrataCache data) that the errata is not applicable to servers that it actually is applicable to, causing them to not get the errata update action scheduled.
Committing to Spacewalk master: 80249d8e13919ecc8a6883f93618de9cdec04d5a
Moving bugs to ON_QA as we move to release Spacewalk 2.3
A pull request accidentally undid the commit in comment 1, re-doing in Spacewalk master: 746366b3405f9e5a1a6e43651593a9f8126bf715 And cherry-picking into Spacewalk-2.3: 62bd10835d98f3103671c08f0c6c11434ffe94d2
Spacewalk 2.3 has been released. See https://fedorahosted.org/spacewalk/wiki/ReleaseNotes23