Bug 1277015 - Host delete unsuccesful
Summary: Host delete unsuccesful
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.1.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-02 05:02 UTC by Balaji
Modified: 2019-09-26 18:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-07 16:21:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Host delete failure (145.81 KB, image/png)
2015-11-02 05:02 UTC, Balaji
no flags Details

Description Balaji 2015-11-02 05:02:54 UTC
Created attachment 1088459 [details]
Host delete failure

Description of problem:
Deleting an unprovisioned host fails with the error:
Required lock is already taken by other running tasks. Please inspect their state, fix their errors and resume them. Required lock: read Conflicts with tasks: - https://sat-ha.cloud.lab.eng.bos.redhat.com/foreman_tasks/tasks/7ccfdea0-1c4e-479c-9162-a293b9eaab2b


Version-Release number of selected component (if applicable):


How reproducible:

Steps to Reproduce:
1.
Create a Host via satellite and continue trying to provision it. If the provisioning fails for some reason, try to delete using the delete button. If the task is not completed, it fails with the above message.
2.
3.

Actual results:
Host cannot be deleted unless the tasks succeed.

Expected results:
If there is a failure, the host delete button should work.


Additional info:

Comment 2 Balaji 2015-11-17 19:24:46 UTC
This is the error message I recd when I tried to delete the host after successfully cancelling the build:
Required lock is already taken by other running tasks. Please inspect their state, fix their errors and resume them. Required lock: read Conflicts with tasks: - https://satnode3.sysmgmt.bos.redhat.com/foreman_tasks/tasks/49645945-c928-4f62-a52e-9e2eaf5902c6

Comment 5 Brad Buckingham 2017-01-12 14:26:29 UTC
I haven't located another bug that specifically addresses this behavior; however, I also haven't had any luck reproducing on Satellite 6.2.

Balaji,

Are you able to reproduce this on Satellite 6.2?  

If so, can I get you to provide details on the specific scenario as well as attach a foreman-debug?

If not, any objection to closing this bugzilla for now and we can re-open if the issue resurfaces?

Comment 6 Balaji 2017-02-07 15:39:07 UTC
The problem did not happen in 6.2. You can probably close this bug.

Comment 7 Brad Buckingham 2017-02-07 16:21:08 UTC
Thanks Balaji!  I am going to close the bugzilla; however, feel free to re-open if the issue re-occurs.


Note You need to log in before you can comment on or make changes to this bug.