Enhancement #19377
closedInventory with missing signature or only signature should remain in incoming for some time
Description
Today, when an inventory or a signature comes in incoming directory without the other part, we wait for 10s, and then fail is nothing comes.
This behavior deceives the catch-back process of relayd that try to send old inventories that weren't sent for some reason (after 30s minimum).
So, we should:
- let the lone signature or inventory in incoming,
- the next catch-up webapp process deals with it (with hopefully the missing part), checking how old it is,
- once the inventory is too old (1h ? 1d ?), we drop it in failed
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by François ARMAND almost 3 years ago
- Tracker changed from Bug to Architecture
- Priority deleted (
0)
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.19 to 6.1.20
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.20 to 6.1.21
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
Updated by François ARMAND almost 2 years ago
- Tracker changed from Architecture to Enhancement
- Target version changed from old 6.1 issues to relocate to 7.3.0~rc1
- Regression set to No
In 7.1 and up, we could let the inventory in the incoming directory and just let the inventory-cleaner take care of it.
It should be an enhancement, since the architecture is already here to take care of it.
Updated by François ARMAND almost 2 years ago
- Status changed from New to Resolved
- Target version changed from 7.3.0~rc1 to 7.2.5
actually it is already the behavior in 7.2 !