Bug #4748
closed
errors on import manifest should complete dynflow task and display information to user
Added by Thomas McKay almost 11 years ago.
Updated over 6 years ago.
Description
% hammer -v subscription upload --organization-id megacorp --file test/data/megacorp.zip
....this will work first time....
% hammer -v subscription upload --organization-id megacorp --file test/data/megacorp.zip
ERROR 2014-03-20 11:15:13 Exception ForemanTasks::Lock::LockConflict
Manifest upload failed:
ForemanTasks::Lock::LockConflict
In this case, an error importing the manifest happened ("manifest already imported") and this should be a non-error information message to user.
Other cases (such as trying to import that manifest into an org other than megacorp) will generate real error message which should be displayed to user and dynflow task completed anyway (with rollback if necessary).
- Assignee set to Ivan Necas
- Triaged set to Yes
we should just have the dynflow step get skipped and the task end up in stopped:error state vs paused. Paused causes you to not be able to resolve the issue without having to go to the dynflow console.
WORKAROUND:
- navigate to: https://yourhost/foreman_tasks/dynflow
- find the task that is paused with Error
- click on the details for it. Find the step that is errored out, click the 'skip' link
- Resume the task
- Repeat skipping substeps if there are further errors
Once you have the task in the Finished state you can import a manifest
- Translation missing: en.field_release set to 13
- Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1093124
- Status changed from New to Assigned
- Target version set to 45
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Applied in changeset katello|commit:6cb65c11e6743f3aaadabc462f9f33e9d49c8445.
Also available in: Atom
PDF