Project

General

Profile

Actions

Bug #22449

closed

API seems to be locked during host deletion

Added by Anthony Chevalet about 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

During host deletion, every API requests stay blocked until the host is deleted.

To reproduce this behaviour, you can add a "sleep xx" in foreman hooks (before/after destroy). Example:

$ cat config/hooks/host/managed/after_destroy/after_destroy.sh
#!/bin/bash
sleep 90

Run host deletion, example:
`hammer host delete --name myclient.local`

During that time, try some get requests, example on compute resources:
`hammer compute-resource info --id 47`

This requests will stay blocked until the host get deleted (>90 sec).

Using this kind of request inside hooks (destroy) will block foreman thread indefinitely.

Actions #1

Updated by Anthony Chevalet about 6 years ago

  • Copied from Bug #22070: Foreman hooks seem broken added
Actions #2

Updated by Anthony Chevalet over 5 years ago

  • Copied from deleted (Bug #22070: Foreman hooks seem broken)
Actions #3

Updated by Anthony Chevalet over 5 years ago

  • Fixed in Releases 1.19.1 added
  • Found in Releases 1.15.6 added

I can't reproduce on 1.19RC3, API calls in destroy hook correctly works. Possibly fixed in a previous version.

Actions #4

Updated by Tomer Brisker over 5 years ago

  • Status changed from New to Resolved
  • Fixed in Releases deleted (1.19.1)
Actions

Also available in: Atom PDF