Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Incremental update task failed when one of its install applicable errata task is failed

Version-Release number of selected component (if applicable):
Satellite 6.1 GA Snap 6

How reproducible:
Always

Steps to Reproduce:
1. Install an incremental update on two content hosts (one of the content hosts had goferd stopped)
2. 'Incremental update' task is created
3. Two sub tasks 'Install Applicable Errata' are created  - One of the tasks completed fine and the other had State = stopped, Result = warning. (expected)

Actual results:
The incremental update paused at 87% with error

Expected results:
The incremental update task should complete 100% with warning

Additional info:

Created attachment 1032210 [details]
dynflow error.log

Created attachment 1032211 [details]
production.log

ivan, can you shed some insight into this error?

Thanks!

Update: resuming the task made it complete 100% GREEN

The BulkAction is missing the handling of `skip` event, that is triggered when the bulk task fails. Overriding the `run` method to catch the skip event should do the trick

Created redmine issue http://projects.theforeman.org/issues/10708 from this bug

Moving to POST since upstream bug http://projects.theforeman.org/issues/10708 has been closed
-------------
Justin Sherrill
Applied in changeset commit:bc93b64560fb8757119c665fc7c1a461b8afc463.

Verified in Sat 6.1 GA Snap 8.

Now the 'Incremental Update' task completes with State=stopped, Result=warning statuses.

This bug is slated to be released with Satellite 6.1.

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.