Project

General

Custom queries

Profile

Actions
Copy link

Bug #19570

closed

tasks that hit lock error remain in 'pending'

Added by Justin Sherrill almost 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Adam Ruzicka
Category:
Foreman plugin
Target version:
foreman-tasks-0.9.2
Difficulty:
Triaged:
Bugzilla link:
1460240
Pull request:
https://github.com/theforeman/foreman-tasks/pull/249
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

When performing some action that takes a lock, if another task is holding that lock the task correctly errors. For some reason though, the task is left in 'planning' state. See screenshot for an example.

I'm not sure when this started, but it first started being reported with katello 3.4 (foreman-tasks-0.9.1-1)

Files

lock.jpg View lock.jpg 42.4 KB Justin Sherrill, 05/16/2017 01:37 PM

Related issues 1 (0 open — 1 closed)

Related to foreman-tasks - Bug #18963: use the new batch processing feature for bulk tasksClosedAdam Ruzicka03/21/2017Actions
#1

Updated by The Foreman Bot almost 8 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Adam Ruzicka
  • Pull request https://github.com/theforeman/foreman-tasks/pull/249 added
#2

Updated by Adam Ruzicka almost 8 years ago

  • Category set to Foreman plugin
  • Target version set to 1.13.1
#3

Updated by Adam Ruzicka almost 8 years ago

  • Related to Bug #18963: use the new batch processing feature for bulk tasks added
#4

Updated by Adam Ruzicka almost 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
#5

Updated by Ivan Necas almost 8 years ago

  • Translation missing: en.field_release set to 252
#6

Updated by Adam Ruzicka almost 8 years ago

  • Bugzilla link set to 1460240
Actions
Copy link

Also available in: Atom PDF