Project

General

Profile

Actions

Bug #9578

closed

CV:Deleting a CV immediately after removing its published version raises 500 ISE

Added by Walden Raines about 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web UI
Target version:
Difficulty:
medium
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1117753
Description of problem:
I was trying a specific scenario to delete to a CV. I created a CV and published it and promote it to next env. Later, I created a new activation-key and selected same cv. Now when I tried to delete CV, UI says: To delete CV, first remove its version and move the associated entities (activation-key) to other CV or env. I followed same and removed the version. On removing the CV version, UI raises notification:

"Successfully initiated removal of testcv2 version 1."

After above notification, I tried to remove the CV and got following error on UI:

Required lock is already taken by other running tasks. Please inspect their state, fix their errors nad resume them. Required lock: read Conflicts with tasks: - https://dhcp207-190.lab.eng.pnq.redhat.com/foreman_tasks/tasks/1b44ce3f-c919-4b87-af1c-3b9701948f69

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140626.1

How reproducible:
always

Steps to Reproduce:
1. create a CV (cv1), publish it and promote it to next env (dev)
2. create activation-key(ak), select 'dev' env and 'cv1'
3. Now try to delete CV
4. first UI will sk to delete its version.
5. Once you triggered version deletion, immediately try to delete CV too

Actual results:
UI raises:

Required lock is already taken by other running tasks. Please inspect their state, fix their errors nad resume them. Required lock: read Conflicts with tasks: - https://dhcp207-190.lab.eng.pnq.redhat.com/foreman_tasks/tasks/1b44ce3f-c919-4b87-af1c-3b9701948f69

Expected results:
UI should raise proper message, saying that deletion is still on-going or something like that and log shouldn't be filled with 500 ISE

There are several other cases, related to locking, and all needs to be handled properly.

Additional info:

Actions #1

Updated by Walden Raines about 9 years ago

  • Status changed from New to Assigned
Actions #2

Updated by The Foreman Bot almost 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/6040 added
Actions #3

Updated by Walden Raines almost 8 years ago

  • Project changed from foreman-tasks to Katello
  • Category set to Web UI
  • Difficulty set to medium
Actions #4

Updated by Walden Raines almost 8 years ago

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

Updated by Eric Helms almost 8 years ago

  • translation missing: en.field_release set to 144
Actions #6

Updated by Eric Helms almost 8 years ago

  • translation missing: en.field_release changed from 144 to 86
Actions

Also available in: Atom PDF