Project

General

Profile

Bug #7748

In case of networking or server errors, the agent may leave .cfnew files in copy destination

Added by Alexis MOUSSET over 2 years ago. Updated about 1 month ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Agent
Target version:
Target version (plugin):
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Pull Request:
Priority:
54

Description

In case of networking or server errors during file copy, the agent may leave .cfnew files in copy destination.
It happens even when purging is enabled, because purge is disabled in case of networking errors.

It may cause issues when happening in special directories (conf.d, etc.).

History

#1 Updated by Alexis MOUSSET over 2 years ago

Reproduce by stopping the server during a GET request. If the file is the last in its directory, the purge is done if enabled, if not it is never done (because a SYNCH will follow and return with error).

#2 Updated by Alexis MOUSSET over 2 years ago

In case of GET error, we should:
  • clean the .cfnew file
  • abort file transfer (especially to disable purge)

#3 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.18 to 2.11.19

#4 Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 2.11.19 to 2.11.20

#5 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.20 to 2.11.21

#6 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.21 to 2.11.22

#7 Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 2.11.22 to 2.11.23

#8 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 2.11.23 to 2.11.24

#9 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 2.11.24 to 308

#10 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 308 to 3.1.14

#11 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.14 to 3.1.15

#12 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.15 to 3.1.16

#13 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.16 to 3.1.17

#14 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.17 to 3.1.18

#15 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.18 to 3.1.19

#16 Updated by Jonathan CLARKE over 1 year ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Infrequent - complex configurations | third party integrations

#17 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.19 to 3.1.20
  • Priority set to 0

#18 Updated by Jonathan CLARKE about 1 year ago

  • Priority changed from 0 to 41

#19 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.20 to 3.1.21

#20 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.21 to 3.1.22

#21 Updated by Benoît PECCATTE 12 months ago

  • Priority changed from 41 to 54

#22 Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 3.1.22 to 3.1.23

#23 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 3.1.23 to 3.1.24

#24 Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 3.1.24 to 3.1.25

#25 Updated by Vincent MEMBRÉ 7 months ago

  • Target version changed from 3.1.25 to 387

#26 Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 387 to 4.1.10

#27 Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 4.1.10 to 4.1.11

#28 Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 4.1.11 to 4.1.12

#29 Updated by Vincent MEMBRÉ about 1 month ago

  • Target version changed from 4.1.12 to 4.1.13

Also available in: Atom PDF