User story #3139
closedMove broken received inventories to a separate directory
Added by Fabrice FLORE-THÉBAULT almost 12 years ago. Updated over 9 years ago.
Description
when a faulty inventory from a node has arrived in /var/rudder/inventories/incoming/
, and the processing of the inventory fails (for example UUID is missing), then the faulty inventory stays in /var/rudder/inventories/incoming/
and can't be overwritten by a new (hopefully not faulty) inventory sent by the node.
Updated by François ARMAND almost 12 years ago
- Status changed from New to 8
- Assignee set to Matthieu CERDA
- Priority changed from N/A to 2
We need to look to our Apache webdav configuration to see how to have the behaviour: each time a "put file" is send, override any existing file.
Updated by Matthieu CERDA almost 12 years ago
- Target version changed from 2.3.10 to 2.3.11
Updated by François ARMAND over 11 years ago
It could be easier to have our sript that takes inventory from the webdav directory to send them to Rudder have to always move the file in an other directory (error inventories, for example for that case).
Updated by François ARMAND over 11 years ago
And it could be great to append the timestamp to the filename, to know when the problem occured.
Updated by Matthieu CERDA over 11 years ago
- Status changed from 8 to Discussion
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
I suggest to change the /var/rudder/tools/send-clean.sh script, which sends the inventory to the endpoint on the Rudder server side, adding a small part that moves the failed file to a special location:
# Abort if sending failed if [ ${SEND_COMMAND_RET} -ne 0 ]; then if [ ! -d "${FAILEDDIR}" ]; then mkdir -p ${FAILEDDIR} fi mv "${FILENAME}" "${FAILEDDIR}/${BASENAME}-$(date --rfc-3339=date)" exit ${SEND_COMMAND_RET} fi
Is this acceptable ?
Updated by Matthieu CERDA over 11 years ago
- Target version changed from 2.3.11 to 2.3.12
Updated by Matthieu CERDA over 11 years ago
- Target version changed from 2.3.12 to 2.3.13
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.3.13 to 84
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 84 to 2.4.7
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.7 to 2.4.8
Updated by Jonathan CLARKE about 11 years ago
- Assignee changed from Jonathan CLARKE to Matthieu CERDA
Matthieu, this looks like a great approach. Please go ahead and implement it.
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.8 to 2.4.9
Updated by Matthieu CERDA about 11 years ago
- Status changed from Discussion to In progress
Acknowledged. Task started.
Updated by Matthieu CERDA about 11 years ago
- Tracker changed from Bug to User story
- Subject changed from on the server, if processing incoming inventory has error, is stays in incoming and new inventory can't be sent to Move broken received inventories to a separate directory
- Status changed from In progress to 13
Updated by Matthieu CERDA about 11 years ago
- Status changed from 13 to 10
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
Updated by Matthieu CERDA about 11 years ago
Task completed, awaiting subtask review / merge.
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.9 to 2.4.10
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.10 to 2.4.11
Updated by Nicolas PERRON about 11 years ago
- Target version changed from 2.4.11 to 2.4.12
Updated by Vincent MEMBRÉ about 11 years ago
- Target version changed from 2.4.12 to 2.8.0~rc1
This fix implies a lot of changes onf the general behavior and therefore will be fixed in 2.8.
This will be fixed in 2.8.0.
As of 2.4, 2.6 and 2.7, we will document the workaround (deleting faulty inventories from /incoming, see #4095).
Updated by Matthieu CERDA about 11 years ago
- Status changed from 10 to 12
- Assignee changed from Jonathan CLARKE to Matthieu CERDA
Updated by Matthieu CERDA about 11 years ago
- Status changed from 12 to Pending release
Applied in changeset packages:commit:3c69950fb2915ff4d0412495ad4138a4d281df21.
Updated by Jonathan CLARKE about 11 years ago
Applied in changeset packages:commit:f8cd73a391935f900bf585724fc47b2742c27318.
Updated by Jonathan CLARKE about 11 years ago
- Status changed from Pending release to 12
Updated by Matthieu CERDA about 11 years ago
- Status changed from 12 to Pending release
Updated by Vincent MEMBRÉ about 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.0~rc1, which was released on Friday 25/10/2013.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-October/000057.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog28
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by Benoît PECCATTE over 9 years ago
- Category changed from 26 to Web - Nodes & inventories