Project

General

Profile

Actions

Bug #2415

closed

Rudder Configuration Rules reports error when a copy of file is initiated and requires a lot of time to be done.

Added by Nicolas PERRON about 12 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
1
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

François BAYART has encountered this bug when trying to copy some files which take 4 mins to be done.


Subtasks 1 (0 open1 closed)

Bug #2470: PT copyGitFile: make copy method configurable (md5, mtime, ctime, etc)ReleasedNicolas PERRON2012-04-24Actions
Actions #1

Updated by Nicolas CHARLES about 12 years ago

The FileCopy PT may take more than 4 minutes, and then all subsequent promises may be delayed out of the next execution, or even skipped du to the ifelapsed.
One solution may be to allow for another usage of the PT, without digest, and idealy to background the copy

Actions #2

Updated by Jonathan CLARKE about 12 years ago

  • Status changed from New to Released
  • % Done changed from 0 to 100

Looks good to me.

Actions #3

Updated by Francois BAYART about 12 years ago

  • Status changed from Released to Discussion

the initial problem still exist in PT version 1.4.

My source directory details are :
86Mo
4744 files
931 directories

Actions #4

Updated by Matthieu CERDA about 12 years ago

  • Description updated (diff)
Actions #5

Updated by Jonathan CLARKE about 12 years ago

For the record: the fix applied for this bug was to allow PIs to be configured to use different file comparaison methods, ie mtime or a MD5 hash. MD5 hashes take longer than mtime, so we had hope this would ease this situation along.

However, the real fix would be to run copy promises asynchronously - or at least at the end of the CFEngine run. I will detail this in another ticket.

Actions #6

Updated by Nicolas PERRON almost 12 years ago

  • Target version changed from 2.3.7 to 2.3.8
Actions #7

Updated by Nicolas PERRON almost 12 years ago

Jonathan CLARKE wrote:

For the record: the fix applied for this bug was to allow PIs to be configured to use different file comparaison methods, ie mtime or a MD5 hash. MD5 hashes take longer than mtime, so we had hope this would ease this situation along.

However, the real fix would be to run copy promises asynchronously - or at least at the end of the CFEngine run. I will detail this in another ticket.

As you said, the fix would be to run copy promises asynchronously, so the fix applied is a simple bypass which can not resolve this bug. Indeed, a new bug as been opened here: #2470 which is relative to the "simple bypass".

Actions #8

Updated by Jonathan CLARKE almost 12 years ago

  • Project changed from Rudder to 24
  • Category deleted (Techniques)
Actions #9

Updated by Nicolas PERRON almost 12 years ago

  • Category set to Policy Templates

It concerns Policy Templates

Actions #10

Updated by Jonathan CLARKE almost 12 years ago

  • Target version changed from 2.3.8 to 2.3.9
Actions #11

Updated by Jonathan CLARKE over 11 years ago

  • Assignee deleted (Nicolas PERRON)
Actions #12

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.3.9 to 2.3.10
Actions #13

Updated by François ARMAND over 11 years ago

  • Category changed from Policy Templates to Techniques
Actions #14

Updated by Matthieu CERDA about 11 years ago

  • Target version changed from 2.3.10 to 2.3.11
Actions #15

Updated by Matthieu CERDA about 11 years ago

  • Target version changed from 2.3.11 to 2.3.12
Actions #16

Updated by Matthieu CERDA almost 11 years ago

  • Target version changed from 2.3.12 to 2.3.13
Actions #17

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 2.3.13 to 84
Actions #18

Updated by Nicolas PERRON almost 11 years ago

  • Target version changed from 84 to 2.4.7
Actions #19

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions #20

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions #21

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.9 to 2.4.10
Actions #22

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.10 to 2.4.11
Actions #23

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.11 to 2.4.12
Actions #24

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.4.12 to 2.4.13
Actions #25

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.4.13 to 2.6.11

I don't understand if this bug is fixed or not... need to test it.

Retargeting to 2.6, since 2.4 is not maintained anymore

Actions #26

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions #27

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions #28

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions #29

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions #30

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions #31

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions #32

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions #33

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions #34

Updated by François ARMAND about 9 years ago

  • Status changed from Discussion to New
  • Assignee set to Benoît PECCATTE
  • Target version changed from 2.6.20 to 2.10.10

Like Vincent, I'm not sur of the status of that one. I understand it's still here and that #2470 only allows to workaround it.

Benoit, could you please qualify again that bug in 2.10, so we have a clear understanding of its status.

Actions #35

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions #36

Updated by Benoît PECCATTE about 9 years ago

  • Status changed from New to Rejected

In 2.10 the technique version 1.3 is available and allow to choose between file comparison methods and provides a mtime option.
A test show that os solves this bug.
Running copy asynchronously is not practical since we would loose the "repaired" event and postprocessing hooks would not work.
Running a directive asynchronously is not a bug and should be tracked in a wishlist.

Actions #37

Updated by Benoît PECCATTE about 9 years ago

  • Project changed from 24 to Rudder
  • Category changed from Techniques to Techniques
Actions

Also available in: Atom PDF